Wildfire Notification

[lmullane]

• As an FOI applicant requesting Ministry of Forests records
• I want a notification about response times
• so that I know my request may be impacted

Assumptions & Scope What are the assumptions for this story?

Staff are deployed in regions. Ministry has asked applicants to be notified that deployments may impact response times.

There is already a notice for Forestry requests (#2889): Private Zenhub Image

The new notice will be in a separate box with the same colours and styling of the existing notice - see above.

What is IN scope? Update FOI Webform with this content when applicant selects MoF in FOI webform;

Please be advised that, due to the ongoing wildfire and drought-related developments around the Province, many Ministry of Forests personnel have been deployed across the Province to support the response and recovery. While every effort will be taken by staff to manage our FOI responsibilities, our response time may be impacted during this situation.

What is NOT in scope? The existing notification (#2889) will remain unchanged.

Acceptance Criteria

Scenario 1: Ministry of Forests Selected

• GIVEN an applicant is on the select Ministry screen
• WHEN they click on Ministry of Forests
• THEN text will appear above the continue button in red with the words: "Please be advised that, due to the ongoing wildfire and drought-related developments around the Province, many Ministry of Forests personnel have been deployed across the Province to support the response and recovery. While every effort will be taken by staff to manage our FOI responsibilities, our response time may be impacted during this situation."

Scenario 2: Ministry of Forests Unselected

• GIVEN an applicant is on the select Ministries screen and Ministry of Forests is selected
• WHEN they uncheck the selection for Forests
• THEN the text that appears above the continue button will be removed.

...

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. [x] 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?

[milosdes]

Screenshot of added notification: Private Zenhub Image

[lmullane]

Looks good, @milosdes

[lmullane]

AC passed and different request types submitting as expected. Thanks, @milosdes