Redirect and open only part of a split request

* As an analyst
* I want to be able to split a request but only open some of the requests that have been split
* so that I can open a request for Ministry A and get clarification on the request for ministry B

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

What is in and not in scope?

**Acceptance Criteria**

Scenario 1: Split a request that is a partial redirect or clarification

GIVEN the analyst is on the Split Request view
https://jacklyn808742.invisionapp.com/console/FOI---Intake-ckpq19frj032r013q6gpm8t1m/ckpx6mtxp012f013ebi30csot/play
AND more than part of the request is a redirect
AND the request descriptions have been filled
AND the date ranges have been specified
WHEN the analyst clicks in the toggle next to for "Does part of this request needed to be clarified and redirected?"
THEN the a request description box will appear for the ministry selected
AND a request description will appear for the Redirect or Clarification
https://jacklyn808742.invisionapp.com/console/FOI---Intake-ckpq19frj032r013q6gpm8t1m/ckpx6mtxp012t013e4wg0agtg/play
AND a file number will have been generated for each ministry selected

**Scenario 2: Cllck 'Create Acknowledgement Letter'**
* GIVEN an intake analyst is on the Open Multiple Ministry Requests modal will open
* https://jacklyn808742.invisionapp.com/console/FOI---Intake-ckpq19frj032r013q6gpm8t1m/ckpx6mtxp012h013egppn0ra5/play
*AND the applicant has provided an email address
* WHEN the applicant clicks the 'Create Acknowledgement Letter' button
* THEN the Correspondence View will open
* https://jacklyn808742.invisionapp.com/console/FOI---Intake-ckpq19frj032r013q6gpm8t1m/ckpybvbw802h7014wf77hd2he/play
* AND multiple request numbers will be the email subject line
* AND the editable email template will be pre-filled for each ministry and redirect
* AND the acknowledgement letter will be attached
* AND the applicant's email will be pre-filled

**Scenario 3: Send Message and Open Requests'**
* GIVEN an intake analyst is Acknowledgement Correspondence View will open
* https://jacklyn808742.invisionapp.com/console/FOI---Intake-ckpq19frj032r013q6gpm8t1m/ckpybvbw802h7014wf77hd2he/play
* WHEN the analyst clicks 'Send Message'
* THEN the email will be sent to the applicant with the attached Acknowledgement Letter
* AND a toast will briefly appear that the email has been sent
* AND only the selected public body requests will be opened, each with a file number
* AND the analyst will be returned to the Request Queue
* AND the selected public body requests will be in the 'Opened' status
* AND the unselected public body requests will be appear in the request queue in an 'Intake' status
* AND the redirected request will be in a 'Redirect' status
* https://jacklyn808742.invisionapp.com/console/FOI---Intake-ckpq19frj032r013q6gpm8t1m/ckpq19gnk00p0011q7zsk81wb/play

...

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

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 by reviewing the Split Request view, the Open Multiple Ministry Requests modal, the Acknowledgement Correspondence View, and the Request Queue described in the acceptance criteria. Clarify the missing assumptions, scope, design, dependencies, and validation rules before implementation; done means the three scenarios work, including selective opening, statuses, file numbers, correspondence, and return to the queue.

Written by the indexing model from the issue text.