Tags - Basic (UXPROD-250)

[UITAG-9] Tags filtering requirements Created: 09/Apr/18  Updated: 04/Oct/21  Resolved: 18/Oct/19

Status: Closed
Project: ui-tags
Components: None
Affects versions: None
Fix versions: None
Parent: Tags - Basic

Type: Story Priority: P3
Reporter: Ann-Marie Breaux (Inactive) Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: phase_1, sprint36, sprint37, tags
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Attachments: JPEG File Filter UX.JPG    
Issue links:
Relates
relates to UITAG-10 Permissions for Tags on Individual Re... Open
relates to UITAG-11 Permissions for Tags on Individual Re... Open
relates to UITAG-12 Permissions for Tags on Individual Re... Open
relates to UITAG-13 Permissions for Tags on Individual Re... Open
relates to UITAG-15 Permissions for Tags on Individual Re... Open
relates to UXPROD-902 Faceted Search Closed
relates to UXPROD-2090 Q4 2019| ACQ apps | Tags cleanup Closed
relates to UIIN-763 Filter Instance by Tags Closed
relates to UIIN-764 Filter Holdings by Tags Closed
relates to UIIN-765 Filter Item by Tags Closed
relates to UINV-81 Filter invoices by tags Closed
relates to UIOR-275 Filter order lines by Tags Closed
relates to UIOR-279 Filter Orders by Tags Closed
relates to UIORGS-116 Filter organizations by tags Closed
relates to UXPROD-2073 Assign Tags to Order records and filt... Closed
Sprint:
Development Team: Prokopovych
Tester Assignee: Ann-Marie Breaux (Inactive)
Epic Link: Tags - Basic

 Description   

Purpose: To be able to filter search results by tags assigned to records within individual apps

As a staff person
I want to be able to filter by tags
So that I can narrow my search results to relevant items

For proof of concept, we can start with the Users app.

Scenarios

  1. Scenario
    • Given the Users app
    • When searching
    • Then the Search and Filter pane on the left side of the screen should display a new section called Tags, as follows:
      • Below the other filter options
      • With the name "Tags"
      • With all the standard filter capabilities
      • See attached screenshot
  2. Scenario
    • Given the Tags filter
    • When the list of tags is displayed in the filter
    • Then it should have the following characteristics
      • Alphabetical order
      • Only display tags used in records in that app, not the entire central tag list
  3. Scenario
    • Given the Tags filter
    • When a tag is assigned to a record in that app, and it was not already listed in the tags filter
    • Then it should appear in the tags filter. Note that the tag may or may not have already existed in the Library's central tag list.
  4. Scenario
    • Given the Tags filter
    • When a tag is unassigned from a record in that app, and that tag is not assigned to any other records in that app
    • Then it should disappear from the tags filter. Note that unassigning a tag from an individual record does not remove the tag from the Library's central tag list.


 Comments   
Comment by Cate Boerema (Inactive) [ 09/Apr/18 ]

Nice story, Ann-Marie Breaux! I'd probably leave off the "Note" on the then statement of scenario 3, as it won't make much sense until after the permissions have been implemented (presumably after this story). Or, if you leave it just for context, please link to the permission storie(s) Also, we should mark this story blocked by STSMACOM-113 Closed .

Thanks!

Comment by Ann-Marie Breaux (Inactive) [ 09/Apr/18 ]

Thanks Cate Boerema - I shortened the note to get rid of the permissions info, and added the blocker. Could you doublecheck? Also since it's blocked, does it stay in Draft, or can it change to Open?

Comment by Cate Boerema (Inactive) [ 12/Apr/18 ]

This is better, though I think mention of the "central tag list" is premature. Otherwise looks great and I think you can mark it blocked. Thanks!

Comment by Ann-Marie Breaux (Inactive) [ 18/Oct/19 ]

Already done as part of the agreements tags work, and now implemented in Orders as well. So closing this as a duplicate

Generated at Fri Feb 09 00:08:22 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.