Feature Update/Change - Divisional Tracking Due Dates

[m-prodan]

• As a Ministry user
• I want to be able to backdate Ministry due dates
• so that I can accurately track and report on items, if certain key fields were misentered, or entered late.

Assumptions & Scope This story is based on user feedback around the divisional tracking.

Currently users can not back date the due date of a divisional stage they enter. They do not have the same restrictions when it comes to completing a response. To address this, we should standardize how dates are picked across both due dates, and received dates.

Due date picker should be updated so that you can pick any date in the past or future, provided that the date is not before the received date (similar to received date picker - #1674)

NOTE Added to this story is another user feedback/request - TRAN would like to have due dates on awaiting fee estimate, so adding this to the functionality.

Also no changes to the general functionality of divisional tracking - comments will still be posted as expected under their current formatting.

What is IN scope? Due dates in the divisional tracker

Acceptance Criteria

Scenario 1: Due Date

• GIVEN a Ministry coordinator is on the review request page
• AND they have selected a division
• WHEN they select a divisional stage that is either: Gathering Records, Awaiting Harms, Pending Sign-Off or Awaiting Fee Estimate
• THEN a field for a due date, that includes a calendar picker consistent with other calendar pickers used in the application

Scenario 2: Due Date Calendar Picker - Activation

• GIVEN a Ministry coordinator has selected a divisional stage that reveals the due date calendar picker
• WHEN they click on the calendar icon
• THEN her or she will active the calendar picker, consistent with other pickers used across the application

Scenario 3: Select Due Date

• GIVEN a Ministry coordinator has activated the calendar picker on a divisional stage
• WHEN they select a date
• THEN the date will appear in the YYYY MM DD Format

Scenario 4: Due Date Selected Can be in the Past

• GIVEN a Ministry coordinator has activated the calendar picker on a divisional stage
• WHEN they attempt to select a date in the past
• THEN they will be able to select that date provided the date is NOT before the request start date

Scenario 5: Save Changes

• GIVEN a Ministry coordinator has selected a divisional stage that reveals the due date calendar picker
• AND all other mandatory fields have been captured in the request
• WHEN they click save changes
• THEN the save toast will appear in the top right corner
• AND The divisional tracking changes will be saved

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?

[m-prodan]

Was going to mention this - but user feedback from Econ sector, with a bit from TRAN (re: due dates on awaiting fee estimate) cc: @lmullane @liseandtea @KyEggleston