Reason a request was Closed on Advanced Search and Queue results

[lmullane]

• As an IAO analyst and ministry coordinator
• I want the reason stated that a request was Closed in the 'Current State' column on Advanced Search and the Queue
• so that I can quickly know why a request was Closed

Assumptions & Scope
What are the assumptions for this story?

Users have asked to quickly know the reason why a request was Closed on their Queue or Advanced Search

What is IN scope?
Add reason for why a request was Closed to the Current State column on Advanced Search and Request Queue

What is NOT in scope?
Closing and selecting a reason a request is Closed #469
Reason a request was Closed on Advanced Search and Queue results #4920

Acceptance Criteria

Scenario 1: Reason a request was Closed on Request Queue

• GIVEN the IAO analyst or ministry in on a Request Queue (My Requests, My Team's Requests, Watching Requests)
• WHEN there is a Closed request(s) listed in the 'Current State' column
• THEN the reason (e.g., Abandoned, Access Denied, Application Fee - Abandoned, Full Disclosure, No Resp. Records Exist/Located, Outside Scope of Act, Partial Disclosure, Records in Another Min/Org, Refuse to Confirm or Deny, Routinely Releasable, Section 43, Transferred, Withdrawn) the request was Closed will appear: Closed - Abandoned

Scenario 1: Reason a request was Closed on Advanced Search

• GIVEN the IAO analyst or ministry in on Advanced Search
• WHEN there is a Closed request(s) listed in the 'Current State' column
• THEN the reason (e.g., Abandoned, Access Denied, Application Fee - Abandoned, Full Disclosure, No Resp. Records Exist/Located, Outside Scope of Act, Partial Disclosure, Records in Another Min/Org, Refuse to Confirm or Deny, Routinely Releasable, Section 43, Transferred, Withdrawn) the request was Closed will appear: Closed - Abandoned

Scenario 3: xxxxxx
...

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]

@JHarrietha-AOT, please advise if this will create any spacing issues for the queue or advanced search?

[m-prodan]

We could maybe have it cut-off after a certain character limit and have a hover over option? I imagine most common ones will be easily perceived at a glance anyways.

Also - not sure if we need scenario 1, since closed requests don't show on the queue. Although OIPC requests may show, they will eventually move to a different state like records review or sign-off.

[KyEggleston]

@lmullane - update scenarios if 'closed - reason for closing' exceeds certain character limit (where it doesn't show up all in advanced search, display full reason for closing on hover.

[sumathi-thirumani]

Internal Technical Refinement (4920):

Estimate: 5

Question (Dev Proposal for display):

1. Similar to the event Queue content column with tooltip for over X characters.
   Update from Bus. Refinement:
   The format will be "Closed - {Reason}. The character limit exceeds the breakable will be shown in tooltip.
   Reference: Event Queue - Column (Content)