Open m-prodan opened 1 year ago
Per refinement - there is a significant amount of work required. Not fully estimated, but consider keeping things as is for now. Alternative options could include an admin screen - but it would also come with a large amount of effort. Will icebox for time being.
Assumptions & Scope As more IAO users and requests get brought into the system, we are running into a higher likelihood of analysts moving across teams. When analysts move across teams, they often keep some of their requests with them. When users change teams, their requests no longer appear - right now analysts have to go to their requests and assign them to themselves as part of their new team.
There are two scenarios to cover - one where an IAO analyst moves to a new team, and another where an IAO analyst has their access to the application revoked.
What is IN scope? Request assignments for IAO users
What is NOT in scope? Ministry user assignments should NOT persist requests across when they have to move teams (either to a new ministry, or to IAO)
Acceptance Criteria
Scenario 1: IAO User Team Change - IAO
Scenario 2: IAO User - Access Revoked
Dependencies? What is the impact of this dependency? (If so, link dependency in the ticket, make it visible in a team´s backlog)
Validation Rules? (If yes, list here)
Design @xxx - please link the Design here
Definition of Ready
Definition of Done