Add a assigned and unassigned filter to Advanced Search

[lmullane]

• As an IAO analyst or ministry coordinator
• I want to filter Advanced Search by 'Assigned' and 'Unassigned'
• so that I can quickly find new requests that can be assigned or that are already assigned

Assumptions & Scope
What are the assumptions for this story?

The CFD supporting processing teams are finding it difficult to action and find requests on their requests queues because they have a lot of unassigned requests (CFD).

Unassigned = assigned to the team = not assigned to an individual.

If a request is watched but assigned to a team, the request will be consider unassigned.

A user can only select 'Assigned' or 'Unassigned' at one time, not both.

What is IN scope?
Add all 'Assigned' and 'Unassigned' as clickable search boxes on Advanced Search.

What is NOT in scope?
#4837 Unassigned request queue
#4920 Reasons for Closed request on Advanced Search

Acceptance Criteria

Scenario 1: All Request States

• GIVEN an IAO analyst or ministry coordinator is logged in
• WHEN they are on Advanced Search
• THEN they will see checkboxes for 'Assigned' (individual user) and 'Unassigned' (team)

Scenario 2: IAO Apply search - Assigned

• GIVEN an IAO analyst is on Advanced Search
• AND they have clicked the checkbox next to 'Assigned'
• WHEN they click the Apply Search button
• THEN only the requests Assigned to an individual IAO user will appear in the Advanced Search results
• • AND the results will be ordered alphabetically by assignee name

Scenario 3: Ministry Coordinator Apply search - Assigned

• GIVEN a ministry coordinator is on Advanced Search
• AND they have clicked the checkbox next to 'Assigned'
• WHEN they click the Apply Search button
• THEN only the requests Assigned to an individual ministry coordinator will appear in the Advanced Search results

Scenario 3: IAO Apply search - Unassigned

• GIVEN an IAO analyst is on Advanced Search
• AND they have clicked the checkbox next to 'Assigned'
• WHEN they click the Apply Search button
• THEN only the requests assigned to IAO teams will appear in the Advanced Search results
• AND the results will be ordered alphabetically by team name (i.e., Central and Economy, Children and Education, Children and Family...)

Scenario 3:Ministry Coordinator Apply search - Assigned

• GIVEN a ministry coordinator is on Advanced Search
• AND they have clicked the checkbox next to 'Assigned'
• WHEN they click the Apply Search button
• THEN only the requests Assigned to an individual ministry coordinator will appear in the Advanced Search results

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]

Hey @lmullane - this one looks good, but it looks like you have the unassigned team queue also baked into this story? The story you reference for the unassigned team queue in the scoping section appears to be a different ticket altogether.

Only other comment - I think we just need a scenario for Ministry search when a request is unassigned.

[KyEggleston]

@lmullane - Reviews ACs in this ticket with #4837 and clean up conflicts/confusion.

[sumathi-thirumani]

Internal Technical Refinement (4927):

Estimate: 8

Open Questions:

1. The reason to have this story besides 4837
2. UX design is pending
3. Request to remove the ACs taken over from 4837.

Update from Bus. Refinement:
ACs will be updated by Loren i.e. remove the queue ACs and retain only the search.
Besides the unassigned queue story; this is also created based on the ask by "Users". However 4837 takes high precedence in delivery over this.