Intake Team - Delete Requests

[m-prodan]

• As an Intake User
• I want to be able to delete a request
• so that I can remove requests that were inadvertently opened in error

Assumptions & Scope This story is a function that will eventually need to be incorporated into the application. Sometimes the intake team opens requests in error, and needs to rectify it by deleting the request in question.

This feature should only be available to the Intake team.

Design will be needed to incorporate some of these components.

What is IN scope?

What is NOT in scope?

Acceptance Criteria

Scenario 1: Options Menu (tbd)

• GIVEN an IAO Intake Team User is on a request
• WHEN they click on the options menu (design element needed)
• THEN there will be additional options that appear including 'Delete Request'

Scenario 2: Click Delete Request

• GIVEN an Intake team user has activated the options menu
• WHEN they click on delete request
• THEN a modal will appear with the message (design needed) and the options to confirm and cancel

Scenario 3: Click Cancel

• GIVEN an Intake user is in the delete request modal
• WHEN they click cancel
• THEN the modal will close and the user will be returned to the request

Scenario 4: Click Confirm

• GIVEN an Intake user is in the delete request modal
• WHEN they click Confirm
• THEN the modal will close and the user will be returned to their home page
• AND the request will be deleted from the system

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?

[lmullane]

@m-prodan, could you confirm if all of IAO would need to do this or only Intake.

Once Deleted a request would no longer be included into the performance stats as it was not an actual FOI request (opened by accident, duplicate).