IAO Task Reminder/Notification Feature

* As an IAO user
* I want to create a task reminder for a request
* so that I know when I need to follow up on something that is not currently tracked/automated

**Assumptions & Scope**
We have received general user feedback regarding the need to be able to establish task reminders on a file.

As a means to address this, we want to leverage existing functionality we have with divisional tracking for Ministry coordinators, and give something similar to IAO users.

IAO users will be able to create one or more custom task reminders - instead of divisions, these will be free text fields with a character limit of 50 characters), and an associated due date calendar picker. These notification reminders will NOT be posted to the comment log, they will simply trigger a notification to the IAO assignee. The Ministry user will NOT receive a notification from these tasks.

What is IN scope?
A custom notification that can be triggered by due dates.

We will use the design/UI features of divisional tracking, place at the bottom of the review request page for IAO users.

What is NOT in scope?
No task reminders will be posted as a system generated comments
Notifications should not be delivered to Ministry users, only assigned IAO users.

**Acceptance Criteria**

**Scenario 1: IAO Request View - Task Reminders**
* GIVEN an IAO analyst is on the request details view of a request
* WHEN they scroll to the bottom
* THEN they will see an area titled 'Task Reminders'

**Scenario 2: IAO Task Reminder**
* GIVEN an IAO analyst is on the task reminder section
* WHEN they click on the task field
* THEN they will be able to enter text

**Scenario 3: IAO Task Reminder - Character**
* GIVEN an IAO analyst has clicked on the task field
* WHEN they start typing characters and exceed 50 characters
* THEN the box will turn red
* AND a message will appear below that there is a character limit of 50

**Scenario 4: IAO Task Reminder - Calendar**
* GIVEN an IAO analyst is on the task reminder
* WHEN they click on the reminder date field
* THEN a calendar picker will appear
* AND will default to todays date

**Scenario 5: IAO Task Reminder - Calendar Date**
* GIVEN an IAO analyst is on the calendar picker for the task reminder
* WHEN they click on a date prior to the received date of the request
* THEN the date will not be selectable

**Scenario 6: IAO Task Reminder - Date Selection**
* GIVEN an IAO analyst is on the calendar picker for the task reminder
* WHEN they click on a valid date
* THEN the picker will close
* AND the reminder date will populate

**Scenario 7: IAO Task Reminder - Add Task**
* GIVEN an IAO analyst is on the task reminder section
* WHEN they click on the plus symbol
* THEN another task reminder field will appear

**Scenario 7: IAO Task Reminder - Delete Task**
* GIVEN an IAO analyst is on the task reminder section
* WHEN they click on the trash can symbol
* THEN the task reminder will be removed
* AND any active notification reminders set for this task will be cleared

**Scenario 8: IAO Task Reminder - Activate Save**
* GIVEN an IAO analyst is on the task reminder section
* WHEN they enter text for a task
* AND have made a valid date selection
* THEN the save button will be active

**Scenario 9: IAO Task Reminder - Activate Save**
* GIVEN an IAO analyst is on the task reminder section
* AND they have entered valid text and date for a task
* WHEN they click save
* THEN the task reminder will be saved

**Scenario 10: IAO Task Reminder - Notification Due Date**
* GIVEN an IAO analyst has saved a valid task
* WHEN it is on the day of the reminder date
* THEN a notification will trigger to IAO USERS ONLY with the following message "(Task Reminder) Is Due Today"

**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 at the request details view and inspect the existing divisional tracking functionality, since the issue says its design and UI should be reused. Confirm the design and the entry points for saving reminders and sending due-date notifications; no files or tests are named. Done means the listed reminder UI, validation, persistence, deletion behavior, and IAO-only notification scenarios pass acceptance testing.

Written by the indexing model from the issue text.