Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-8975

Ability to configure quick filters to function as OR searches instead of AND searches

    • Icon: Suggestion Suggestion
    • Resolution: Answered
    • None
    • None
    • None
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      It would be convenient if I could configure quick filters to function as an OR search.

      For instance, if I use a set labels for my various user stories, where each story is assigned one label, it would be nice to be able to create quick filters for each label, and then use the filters in Plan or Work mode to only view issues with, for example, labels 'A', 'B', and 'C' at the same time.

      Currently, if I click on filters 'A' and 'B', nothing will shows up, since quick filters function as an AND search.

      I know that I could define the filters as Labels != "A", and so on, but it would be preferred to simply be able to configure a board to apply quick filters as an OR search.

      (I initially tried creating this issue in the GreenHopper project, but it does not have an 'Improvement' issue type, so I'm creating it here in the JIRA project instead. Hope that's okay.)

            [JSWSERVER-8975] Ability to configure quick filters to function as OR searches instead of AND searches

            +1

            Absurd that slightly more sophisticated filter logic isn't supported.

            Eric Cooper added a comment - +1 Absurd that slightly more sophisticated filter logic isn't supported.

            All this activity, yet not even being considered by Atlassian... what a shame.
            Let's hope they listen to https://jira.atlassian.com/browse/JSWSERVER-20741 ...

            jonas.dekegel added a comment - All this activity, yet not even being considered by Atlassian... what a shame. Let's hope they listen to https://jira.atlassian.com/browse/JSWSERVER-20741  ...

            I think best would be to have filter groups, where filters in the same group would be ORed and the entire group will then be ANDed.
            Eg if you have following `filters(groups)`:

            • backend (group:team)
            • frontend (group:team)
            • TODO (group: status)
            • WIP (group: status)
            • IMPORTANT (group: null)
            • CUSTOM (group: null)

            Then selecting all above would do:
            (backend OR frontend) AND (TODO or WIP) AND (IMPORTANT) AND (CUSTOM)

            h.narozny@advoxstudio.com added a comment - I think best would be to have filter groups, where filters in the same group would be ORed and the entire group will then be ANDed. Eg if you have following `filters(groups)`: backend (group:team) frontend (group:team) TODO (group: status) WIP (group: status) IMPORTANT (group: null) CUSTOM (group: null) Then selecting all above would do: (backend OR frontend) AND (TODO or WIP) AND (IMPORTANT) AND (CUSTOM)

            +1.

            It's trivial and with virtually no impact on previous UX, IMO... It's just common sense. It's something so obvious that, even knowing it doesn't work like that, I still often find myself clicking on more than one quick filter trying to get the union of result sets...

            The best thing would be having a switch ("Any/All").

            Deleted Account (Inactive) added a comment - +1. It's trivial and with virtually no impact on previous UX, IMO... It's just common sense. It's something so obvious that, even knowing it doesn't work like that, I still often find myself clicking on more than one quick filter trying to get the union of result sets... The best thing would be having a switch ("Any/All").

            +1

            Paul Lewin added a comment -

            It's a real shame this feature has not been regarded for implementation. Both on Kanban and Scrum Boards it would make things sooo much easier.
            If like me, you really miss this functionality, perhaps we can start voting on this new ticket JRACLOUD-69062.

            Paul Lewin added a comment - It's a real shame this feature has not been regarded for implementation. Both on Kanban and Scrum Boards it would make things sooo much easier. If like me, you really miss this functionality, perhaps we can start voting on this new ticket  JRACLOUD-69062 .

            +1

            +1

            +1

            Sunny added a comment -

            +1

            Sunny added a comment - +1

              Unassigned Unassigned
              b375f3459a6c Mislav Kos
              Votes:
              10 Vote for this issue
              Watchers:
              74 Start watching this issue

                Created:
                Updated:
                Resolved: