History of updates to the Applicant Profile

* As an IAO analyst
* I want to see the a history of updates to applicant profiles
* so that I know what updates were made

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

IAO analysts will update applicant profiles with new information, such as phone numbers and emails.

IAO will want a log of updates:

- What was updated?
- Who made the update?
- When did the update occur?

Change log should be similar to CFR version history.

What is IN scope?

What is NOT in scope?
Edit and Save changes to an Applicant Profile #4769
View and select existing Applicant Profile #4761
Creating a new applicant profile
Searching and selecting profiles for On Behalf of requests
Adding an additional applicant category profile (i.e. different applicant type) #4763
Request History for an applicant

**Acceptance Criteria**

**Scenario 1: Applicant Profile Change Log**
* GIVEN updates have been made an an applicant profile
* WHEN the analyst is on the Applicant Profile
* THEN there will be a link for the 'Applicant Profile Change Log'

**Scenario 2: No Applicant Profile Change Log**
* GIVEN no changes have been made to an applicant profile
* WHEN the analyst is on the Applicant Profile
* THEN there will be no link for the 'Applicant Profile Change Log'

**Scenario 3: Click Applicant Profile Change Log - one change made**
* GIVEN there has been one change made to an applicant profile
* AND an analyst is on the Applicant Profile
* WHEN the analyst clicks on the 'Applicant Profile Change Log link
* THEN the Change Log will open
* AND what is changed will be listed (e.g. phone number, email, etc)
* AND the username who made the change will be displayed
* AND the date stamp when the change was made will be displayed

**Scenario 4: Click Applicant Profile Change Log - more than one change made**
* GIVEN there has been more than one change made to an applicant profile
* AND an analyst is on the Applicant Profile
* WHEN the analyst clicks on the 'Applicant Profile Change Log link
* THEN the Change Log will open
* AND the updates made to the Applicant Profile will be listed from newest to oldest
* AND the latest change will be open
* AND all other changes will be closed
* AND the username and date stamp will be visible for closed change

**Scenario 5: Click change with closed accordion**
* GIVEN there has been more than one change made to an applicant profile
* AND an analyst is on the 'Applicant Profile Change Log link
* WHEN the analyst clicks on a closed change
* THEN the change will open
* AND what is changed will be visible (e.g. phone number, email, etc)
* AND the username who made the change will be displayed
* AND the date stamp when the change was made will be displayed

**Scenario 5: Click change with open accordion**
* GIVEN there has been more than one change made to an applicant profile
* AND an analyst is on the 'Applicant Profile Change Log link
* WHEN the analyst clicks on an open change
* THEN the change will close
* AND what is changed will no longer be visible (e.g. phone number, email, etc)
* AND the username who made the change will be displayed
* AND the date stamp when the change was made will be displayed

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

No files, tests, entry points, design, or linked dependencies are named. Start by resolving the missing scope and design with the product team, then identify the Applicant Profile view and its change-history data path; done means the listed acceptance scenarios pass, including ordering, accordion state, changed fields, username, and timestamp.

Written by the indexing model from the issue text.