Clicking on Contact button

* As an FOI Intake Analyst
* I want to email somebody about the request
* so that I can get additional information

**Assumptions & Scope**
Analyst has clicked on an unopened request in the queue of the homepage
"Review request" is currently selected in the left sidebar

What is in and not in scope?
Sending/Receiving of Email is not in scope of this issue.
Email fields for the Email Details page are covered in #104

**Acceptance Criteria**

**Scenario 1: Contact Applicant from Review request screen**
* GIVEN ... I am on the review request page of a request
https://jacklyn808742.invisionapp.com/console/share/3W2O64AP5C/736503621
* WHEN ... I click the "contact" button in the upper right window
* THEN ... left sidebar changes to "Correspondence Log" https://jacklyn808742.invisionapp.com/console/share/3W2O64AP5C/657932512
* AND ... window changes to show "email details" fields

**Scenario 2: Contact Applicant from Correspondence screen**
* GIVEN ... I am on the correspondence log page of a request
https://jacklyn808742.invisionapp.com/console/share/3W2O64AP5C/657932510
* WHEN ... I click the "contact" button in the upper right window
* THEN ... left sidebar remains on "Correspondence Log" https://jacklyn808742.invisionapp.com/console/share/3W2O64AP5C/657932512
* AND ... window changes to show "email details" fields

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

**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 from the review request and correspondence log entry points, then compare the linked InVision screens for the contact-button transitions and email details view. Done means the contact button changes the sidebar and displayed fields as specified in both scenarios, without implementing email sending or receiving covered by this issue's scope.

Written by the indexing model from the issue text.