Preparing an Email

* As an analyst
* I want to send an email
* so that I can communicate with applicant or colleagues about the request

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

What is in and not in scope?
- Not in scope: Correspondence log, adding attachments
- Ability to fill in email fields or having "Send Message" button become active is not in scope

**Acceptance Criteria**

**Scenario 1: "Indicate required fields"
* GIVEN the analyst is in the Review or Correspondence sections and selects the "Contact" button
https://jacklyn808742.invisionapp.com/console/share/3W2O64AP5C/657932512
* WHEN the view changes to "Email details"
*THEN the "From" dropdown menu will be autoset to IAO email field, "To", "Subject" and "Email Description" will be required fields with an asteriks and red text

**Scenario 2: "Activate Save draft button"
* GIVEN the analyst is in the Review or Correspondence sections and selects the "Contact" button
https://jacklyn808742.invisionapp.com/console/share/3W2O64AP5C/657932512
* WHEN the view changes to "Email details"
*THEN the "Save Draft" button is active but "Send Message" button is inactive (greyed out)

**Scenario 3: 'Save as Draft'**
* GIVEN the 'Save as Draft' button is active
https://jacklyn808742.invisionapp.com/console/share/3W2O64AP5C/657932512
* WHEN the analyst clicks 'Save as Draft'
* THEN the email will be saved
* AND the analyst returns to the Correspondence Log view
https://jacklyn808742.invisionapp.com/console/share/3W2O64AP5C/657932511

**Scenario 4: 'Selecting cc or bcc fields'**
* GIVEN I am on the Email Details page
* WHEN the analyst clicks on "cc" or "bcc" fields in the "To" field
* THEN the fields expand to include "To", "cc" and "bcc"
* AND the analyst can type in those fields

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

**Design**
https://jacklyn808742.invisionapp.com/console/share/3W2O64AP5C/657932512

**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 locating the Review, Correspondence, Contact, Email details, and Correspondence Log entry points in the repository, then compare their behavior with the linked InVision designs. Done means the required fields and button states match the scenarios, cc/bcc fields expand for entry, and saving a draft returns to the Correspondence Log.

Written by the indexing model from the issue text.