Page Comparison

Since the scope of the Trainee View is limited to current functionality, the scope relating to Trainee JIRA tickets should be as follows:

Out of Scope:

Process Name	T-1 New Registration - FURTHER DISCUSSION REQUIRED, maybe make this a sub-story of TIS-629	Comments MVP
Description	User has the ability to register to use the TIS system directly	Is this a necessary story? Do trainees have the ability to request Intrepid access? Do we need same/separate login details for new TIS, so migration consideration? Trainees will not be requesting access we will send creds out as part of the onboarding process. We will have to consider how we migrate the current trainees onto TIS.
Actors	Trainee
Pre-Conditions	TBC
Post-Conditions	Trainee has access to new TIS system - login / logout capability
Process Steps	user register a username user sets password user sets security user validates details system shares	What interaction should this have with Admin UI? What are the back end implications? User able to change their password once logged in for the first time. User name will be email address. Processes to be done by the admins/system not the trainee.
Alternative Flow	User is registered from <another system>
Rules	TBC	Format of username? Email Validation of password? None What security should be implemented? There will be a trainee 'role' applied to all trainee users.
JIRA Reference	TIS-629	Wider discussion necessary on whether this is a valid story, before writing a JIRA ticket
Audit Log	TBC

...

	T-3 Trainee Logout	Comments MVP
Description	Trainee has the ability to logout of the system
Actors	Trainee
Pre-Conditions	Trainee has been registered on system Trainee has validated their registered details
Post-Conditions	Trainee leaves logged in view of system securely
Process Steps	Trainee selects to logout System logs user out System presents logged out view
Alternative Flow	N/A
Rules	N/A
JIRA Reference	N/A
Audit Log	TBD

...

Versions Compared