Applicant Personal Request Alert (CFD)

* As an FOI applicant
* I want to be able to see an alert
* so that I understand how valuable it is to give all relevant personal information

**Assumptions & Scope**
When an applicant submits a request to MCFD for their personal information it is vital for them to know how important it is to provide all relevant personal contact information, and to be clear on the scope of their request to ensure timely processing.

Example for Ministry of Forest wildfire requests:

We are looking to do something similar here, with wording to be provided at a later date

What is IN scope?

What is NOT in scope?

**Acceptance Criteria**

**Scenario 1: Selecting MCFD for a Personal Request**
* GIVEN An applicant is making a personal FOI request through the online webform
* WHEN They select the Ministry of Children and Family Development
* OR when the system auto-selects the Ministry of Children and Family Development
* THEN an alert will be displayed stating ""

**Scenario 2: Unselecting MCFD for a Personal request**
* GIVEN An applicant is making a personal FOI request through the online webform
* AND the Ministry of Children and family development has been selected
* WHEN They uncheck the Ministry
* THEN the alert displayed will disappear

**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 locating the online webform flow where applicants select or unselect a ministry, then inspect its existing tests and alert patterns. The issue does not name files, tests, final wording, or a design; done means the approved alert appears for a personal MCFD request and disappears when MCFD is unselected.

Written by the indexing model from the issue text.