Make start date field more accurate and intuitive.
Simple wireframe provided by UX... http://5fwh38.axshare.com
Delivery criteria:
Field should only contain dates from 2000 onwards
User should be given the option to allocate 'start at any time' as an alternative to a start date
User should not be able to select 'start at any time' for UKPASS courses
As a course management user I want a link back to the dashboard and back to course list view so that when I'm looking at my courses I can easily navigate away from the courses area
Please check work done on dashboard/provider page for consistency
See attached wireframes (sorry they're not pretty!!)
Fields (in display order) are:
UKPASS course? - y/n - course profile level
Balance indicator - Course profile level, must see buttons that represent each of 5 balance indicator values (below). Field to read 'what is the subject composition of your course?'
JACS information - Course profile level. The number of required JACS codes is determined by the balance indicator, as follows:
ATAS flag - The following statement should appear ONLY when an ATAS flag is applied to the course 'An ATAS certificate is required for this course'
PG ID / Course Code - Field to read 'UKPASS application code'
Course Short title Field to read 'Short course title' up to 20 characters
modular - (y/n) Field to read 'Is this a modular course?'
CPD flag - (y/n) Field to read 'Is this course suitable for maintaining Continued Professional Development (CPD)?'
International Information not mandatory, text field up to 2000 characters Field to read 'Information specific to International applicants', when no data is available display 'no specific international information available'
Delivery criteria:
As a HEP I want to be able to change contact information so that I can keep my information up to date
Query: Impact of user id on seeding?
As a provider I want to have all new fields populated so that my provider details are stored correctly
Seed new fields where data exists in XAP:
Leave provider code empty
There are no incomplete tasks
There are no unfinished stories
Spikes are investigative stories that enable the development team to work out how to solve problems in future stories
There are no completed spikes
There are no unresolved issues
Improvements are items of work that the development teams have identified to improve the product / improve the ways of delivering the product and remove technical debt
There are no Improvements items identified for this release