...
# | User Story | Jira Ticket | Comments |
---|
1 | As a TPD I want to be able to see occupancy of posts and trainees in a programme within a given time window So that I can assign easily assign trainees to vacant posts in a Plan - Person detail should be forename, surname, GMC number
- Once a person is selected we should be able to see any past current or future placement details as well as Programme/curriculum membership detail (What is this. Is this the placement for person. We did not have this in the initial scope. We are looking at placements in a programme. So we are able to see on the timeline past/current and future. But not at the same level that we have for People/placements. Matt will discuss with Ashley).
AP: At the time of searching the person, if we could have a link to the person>placements. - Existing placements need to be visible within the UI - Done
| Jira Legacy |
---|
server | System JIRA |
---|
serverId | 4c843cd5-e5a9-329d-ae88-66091fcfe3c7 |
---|
key | TISNEW-2294 |
---|
|
| - Matt: GMC will be added as a pill by Panos. Matt will supply an example
|
2 | As a TDP I want to be able to see occupancy of posts and trainees in a programme within a given time window - Done So that I can efficiently assign posts to multiple less than full time trainees - Done - Ensure WTE is visible in the UI
| Jira Legacy |
---|
server | System JIRA |
---|
serverId | 4c843cd5-e5a9-329d-ae88-66091fcfe3c7 |
---|
key | TISNEW-2295 |
---|
|
| - Matt: WTE will be in the ’Tooltip rollover’ and also in the modal once you select the trainee
Ashley: - Considerations for the design/display when there are 1 programme with 50 posts for e.g. at same specialty.
- Considerations for the design/display 'Dr Vacant' placements.
|
3 | As a TPD I want to be able to see any overlap between placements So that I can efficiently assign posts to trainees for a programme | Jira Legacy |
---|
server | System JIRA |
---|
serverId | 4c843cd5-e5a9-329d-ae88-66091fcfe3c7 |
---|
key | TISNEW-2296 |
---|
|
| |
4 | As a TPD I want to be able to search for and filter posts and people for a large programme -(We do not require a filter as far as we can determine as we have the ability to search across multiple areas of data. Filtering would require a table of results).- Done So that I can arrange the placements in a Plan format - Ability to filter a list of trainees who have no placement within a specified time range. (Matt to talk to Ashley, where is the value in this? We have search but do not think we need filters, lets discuss, I think value if the results are large, but need to establish this with Ashley)
- Ability to filter a list of posts who have no trainees within a given time range. (Matt to discuss with Ashley as to value of filtering. We have the ability to search, would the user need to filter those searches. We would expect the user to understand what data they were looking for. Ie. A Trainee or a Post).
- Ability to search for trainees by name/GMC number within the UI - Done
| Jira Legacy |
---|
server | System JIRA |
---|
serverId | 4c843cd5-e5a9-329d-ae88-66091fcfe3c7 |
---|
key | TISNEW-2297 |
---|
|
| Ashley: Ability to filter trainees with no placement: this is so that a TPD can put them into placements. We can check with James.Ability to filter posts with no trainees: So that placements can be created for those posts. We can check with James.- Matt to talk to Ashley, where is the value in this? We have search but do not think we need filters, lets discuss, I think value if the results are large, but need to establish this with Ashley)
- JH/AP: Post MVP
|
5 | As a TPD I want to be able to create/edit/delete placements with the searched vacant posts and trainees - Done So that I can include them in the plan - When creating the placement we need to be able to access all the fields associated with a placement on TIS.
- To be able to assign Educational and Clinical supervisors against placements
- Warning when attempting to create a placement against an occupied post
- On creation the UI should save the placement and then take the user to the placement within the plan view
| Jira Legacy |
---|
server | System JIRA |
---|
serverId | 4c843cd5-e5a9-329d-ae88-66091fcfe3c7 |
---|
key | TISNEW-2298 |
---|
|
|
|
6 | As a TPD I want to be able to see and differentiate between the different types of placements (Parental leave, In Post, etc.) So that I can efficiently manage the plan | Jira Legacy |
---|
server | System JIRA |
---|
serverId | 4c843cd5-e5a9-329d-ae88-66091fcfe3c7 |
---|
key | TISNEW-2299 |
---|
|
| Matt: This will be visible in the Modal and Tooltip |
7 | As a TPD I want to be able to organise and save the plan - Done So that I or someone else with relevant permissions can come back later and make changes to it | Jira Legacy |
---|
server | System JIRA |
---|
serverId | 4c843cd5-e5a9-329d-ae88-66091fcfe3c7 |
---|
key | TISNEW-2300 |
---|
|
|
|
8 | As a TPD I want to see the plan with a start date/time of Today's date by default and spanning to 12 months in the future, but should should also be able to adjust the time window So that I can also view past and future Placements. - Done | Jira Legacy |
---|
server | System JIRA |
---|
serverId | 4c843cd5-e5a9-329d-ae88-66091fcfe3c7 |
---|
key | TISNEW-2301 |
---|
|
| - Timeline to be at Programme/Plan level and not per per post as it is currently.
|
9 | As a TPD I want to be able to see the Post detail (National Post Number, Site, Specialty and Grade) on the planner - Post detail should include Post No, Site, Specialty, Grade.
So that I have the site information of the post and easily assign trainees to vacant posts in a Plan. | Jira Legacy |
---|
server | System JIRA |
---|
serverId | 4c843cd5-e5a9-329d-ae88-66091fcfe3c7 |
---|
key | TISNEW-2488 |
---|
|
| - The suggestion from James is to show this under specialty from the current design
|
To_Be - Post MVP
As a TPD for For London Programmes
I want to be able to include rotations in the Placements plan
So that I can manage Rotations for London
...