Since the scope of the Trainee View is limited to current functionality, the scope relating to Trainee JIRA tickets should be as follows: ADD STEVE LIST EQUIVALENCE
- TIS-540
- TIS-684
- TIS-681
- TIS-539
- TIS-683
- TIS-92
- TIS-682
- TIS-278 << NOT REQUIRED, REMOVED FROM JIRA
- NEW STORY REQUIRED - support
- NEW STORY REQUIRED - form R, part A
...
| Process Name | T-1 New Registration - FURTHER DISCUSSION REQUIRED, maybe make this a sub-story of TIS-629 | Comments MVP - move to Admin UM | ||||
| Description | User Admin has the ability to register a user 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 | 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 | TraineeAdmin | |||||
| Pre-ConditionsTBC | Trainee must have registered via Oriel to a particular region | |||||
| Post-Conditions | Trainee has access to new TIS system - login / logout capability | |||||
| Process Steps |
| What interaction should this have with Admin UI? What are the back end implications?
| Admins should be able to trigger welcome message, credentials message, oriel manual upload 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> | |
| Alternative Flow | Non-oriel import (Dentists / Other Academic Trainees) | |||||
| 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 | No need to report on this | Oriel upload to be considered separately |
| Process Name | T-2 Trainee Login FURTHER DISCUSSION REQUIREDLogin | Comments MVP | ||
| Description | Trainee has the ability to login using the details they were registered for the service withWill they be able to use their old details, or have to re-register? | I expect all trainees will require new login credentials but they will not have to 'register' as we will send out logins as and when we migrate trainees to TIS. What about users transitioning from Synapse? What will happen to details there? The process will be the same for Synapse users as they are transitioning from one system to another. | ||
| Actors | Trainee | |||
| Pre-Conditions | Trainee has been registered on systemTrainee has validated their registered details | |||
| Post-Conditions | Trainee is able to view the login space | |||
| Process Steps |
| |||
| Alternative Flow | T-17 Forgotten Username T-18 Forgotten Password T-19 Username / Password Error T-XX: update login details | |||
| Rules |
| |||
| JIRA Reference | N/A to be created | Audit Log | TBD | |
| Monitoring | No users logging in Further discussion required |
| 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 |
| |
| Alternative Flow | N/A | |
| Rules | N/A | |
| JIRA Reference | N/A | |
| Audit Log | TBD |
...