...
As a Local Office Admin
I want to record posts placeholders in a consistent way on TIS following an agreed national process
So that I can produce reports on Code of Practice
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
| # | Question for discussion | Comments |
|---|---|---|
| 1 | How do we record this on TIS to support better code of practice reporting? - Current performance issue of recording huge amount of placeholders on TIS against a post and rendering this on the UI - Data model impacts? - UX/UI: Tick boxes and reasons to record and to report on....suggestion from Lynn? - Impact on Placement Planning Tool development - TIS-ESR Interface impacts if recorded on TIS or change is made to the current way of recording | |
| 2 | Posts level information on TIS that relates to Code of Practice (tbd): - Historical Placements - Recording the vacancy information on the Posts - What vacancy information to record? - Automatic flagging of posts that are vacant/are due to be vacant? - Based on the categories yet to be proposed - Vacancy type: Vacant/On hold/Recruit - Vacancy reason - Date from and to etc. - Export to ESR (Yes/No)? or make available via Trust access? - Last modified placement date - Those information to be available to NDW for reporting | Reduce the human input on TIS. |
| 3 | If the Post vacancy information are new fields other than what we already have on TIS currently, should these be available as a bulk upload facility and made separate? |
...