FOI Ministry Request Queue - Corrections

* As a BC Corrections User
* I want requests for the corrections branch to only be visible to me or my group
* so that I can ensure the highest level of privacy for my applicants

**Assumptions & Scope**
This is a requirement received from the justice sector for onboarding them as a Ministry. Corrections request fall under the Ministry of Public Safety and Solicitor General. A change is being pushed in AXIS to create a corrections action office code (COR)

Assumption: a new keycloak group specifically for PSS-Corrections requests will need to be created
There will be no practical difference in functionality for this queue, it will operate the same as with other Ministry level queues

What is IN scope?
Requests that will appear in the queue for BC Corrections staff

What is NOT in scope?

**Acceptance Criteria**

**Scenario 1: Correction Requests - Call for Records**
* GIVEN a request has the Corrections Action Office code "COR"
* WHEN the state is changed to Call for Records
* THEN the request will be assigned to the PSS - Corrections Team Queue
* AND the request will NOT be visible or searchable to the main PSS Team

**Scenario 2: Correction Requests – Action Office Changed**
* GIVEN a COR request and is in the call for records state or later
* WHEN the action office is changed to PSS
* AND the IAO user syncs the request
* THEN the request will disappear from the corrections queue
* AND the request will appear as an unassigned request in the main PSS Team queue

**Scenario 3: PSS Requests - Change to Corrections**
* GIVEN a request has the action office PSS assigned to it
* WHEN the action office is changed to COR
* AND the IAO user syncs the request
* THEN the request will disappear from the main PSS Team queue
* AND the request will appear as an unassigned request in the corrections queue

**Validation Rules? (If yes, list here)**

**Design**
@xxx - please link the Design here

**Definition of Ready**

1. [ ] Is there a well articulated User Story?
2. [ ] Is there Acceptance Criteria that covers all scenarios (happy/sad paths)?
3. [ ] If there is a user interface, is there a design?
4. [ ] Does the user story need user research/validation?
5. [ ] Does this User Story needs stakeholder approval?
6. [ ] Design / Solution accepted by Product Owner
7. [ ] Is this user story small enough to be completed in a Sprint? Should it be split?
8. [ ] Are the dependencies known/ understood? (technical, business, regulatory/policy)
9. [ ] Has the story been estimated?

**Definition of Done**

1. [ ] Passes developer unit tests
2. [ ] Passes peer code review
3. [ ] If there's a user interface, passes UX assurance
4. [ ] Passes QA of Acceptance Criteria with verification in Dev and Test
5. [ ] Confirm Test cases built and succeeding
6. [ ] No regression test failures
7. [ ] Test coverage acceptable by Product Owner
8. [ ] Ticket ready to be merged to master or story branch
9. [ ] Developer to list Config changes/ Update documents and designs
10. [ ] Can be demoed in Sprint Review
11. [ ] Tagged as part of a Release
12. [ ] Feature flagged if required
13. [ ] Change Management activities done?

No implementation files or tests are named. Start by tracing the existing ministry queue behavior for action-office changes and IAO user sync, then verify the three acceptance scenarios: COR requests move into the Corrections queue, visibility and search isolation hold, and changes between COR and PSS move requests between queues.

Written by the indexing model from the issue text.