Redirect a request in full

* As a FOI analyst
* I want the ability to redirect a request in full
* so that I can provide applicant with the correct organization to contact for their request

**Assumptions & Scope**
What are the assumptions for this story?

What is in and not in scope?

**Acceptance Criteria**

**Scenario 1: Analyst reviews request and identifies it as a redirect**
* GIVEN ... an analyst is on the Review Request page
https://jacklyn808742.invisionapp.com/console/share/3W2O64AP5C/657932454
AND they have received a request that is not relevant to any government ministry
AND category has been selected
* WHEN ... they select a "Redirect in Full" button
* THEN ... a modal will pop up with choices of public bodies
https://jacklyn808742.invisionapp.com/console/share/3W2O64AP5C/657932454

**Scenario 2: Analyst selects where request should be redirected**
* GIVEN ... an analyst is redirecting a request on the redirect modal
* https://jacklyn808742.invisionapp.com/console/share/3W2O64AP5C/657932454
* WHEN .... the analyst select one or more of 12 checkboxes
* THEN ... the checkboxes will appear with a checkmark

**Scenario 3: Analyst selects the request should be redirected to another option not listed**
* GIVEN ... an analyst is redirecting a request on the redirect modal
* WHEN .... the analyst clicks on "other" button
* THEN ... (awaiting design)

**Scenario 4: Analyst selects "Create Redirect Letter"**
* GIVEN ... An analyst is on the redirect modal screen
* AND ... has selected who to redirect a request to
* WHEN .... clicks on "Create Redirect Letter" button
* THEN ... analyst will be taken to a new page for that request under the correspondence log

**Scenario 5: Analyst selects "Return to Queue"**
* GIVEN ... An analyst selects the "Return to Queue" button
* WHEN .... on the "Redirect Request in Full" modal
* THEN ... analyst will be returned to the request queue page

**Dependencies? What is the impact of this dependency? (If so, link dependency in the ticket, make it visible in a team´s backlog)**
Letter generation is not part of this story

**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?

Start with the Review Request page and trace the existing request queue and correspondence-log flow; the issue names no implementation files, tests, or entry points. Before coding, resolve the missing designs and the scope for selecting public bodies and “Other,” then verify the redirect modal, return-to-queue behavior, and navigation to the correspondence log against the acceptance scenarios.

Written by the indexing model from the issue text.