Jira Quick Filters

[Brinda]

Iam trying to create a dashboard gadget based on the Filter Results option but I want to be able to use quick filters (or similar) so that I can either view all filter results, or selecting a quick filter for specific sprints.

I have gone through a variety of the gadgets that seem related but no luck. I have also found this post online which looks exactly like what I want to use but does not seem available on JIRA anymore ( -filters-for-jira-dashboards/)

3 years later and there's sill no option to NOT auto-hide quick filters? This is as annoying as heck from a UI perspective. I do wish Atlassian would give a setting to stop the current behavior and give us what we had with on-prem.

EVERY time I open up my team's Kanban or Scrum (we use both) I have to select to show the quick filters. We have two separate teams working off the queue and during our meetings we need those quick filters to swap back and forth during our discussion. So - we need it EVERY time. Then when we go off to our sub-teams, we then need them again.

That's a lot of extra clicks that were not required previously. This is frustrating, as was mentioned by multiple people previously. The amount of filters before the dropdown kicks in should at least be set manually.

Thank you for your reply Daniel! Sorry for the delay, this is what I mean, when we are on our sprint board page, in the server version the quick filters always displayed. Here as you can see its collapsed and I have to expand the Quick filters dropdown list, to see the filters. I checked both classic and next-gen board and it doesn't make a difference it seems.

Oh, I see now what you mean.

There has been a dicussion along with the recommendation of a "fix" to switch back to old view:

-questions/How-do-we-get-an-expanded-Quick-Filters-view-like-before-the/qaq-p/655029

For the moment this could be a workaround - but new view will be default next year so the behaviour you are facing seems to be set as in "new" standard to handle this.

But switching back to the old view changes nothing with the quick filters, am I not switching the setting in the correct place maybe?

xyzcompany.atlassian.net/secure/ViewPersonalSettings.jspa

Can we disable the dropdown and stop it from doing that? This is a big pain as I have to constantly expand it throughout the day and it's extra work. Any way to make a request? I'm not the only one with this issue even just at my company, I'm sure others are having the same frustration :(. Thanks for the help and response!

The software is designed for many thousands people across the world. What one user considers bad UI is not necessarily true for some other.

You can leave feedback here for Atlassian:

I know, that's why I put a smiley face after my comment above :D. I know you can't please everybody but wanted to get it heard in case it's not just us at our company that this is a feature we really liked in the server version. Thanks a bunch for your replies and help, much appreciated!

It's annoying that Atlassian keeps coming up with these nonsense changes and then their supporters immediately come to their defence. I don't think there will be a single user who wants the Quick filters to be invisible or hidden. Even if someone wants it, there could be an option for that. But here, the default behaviour is changed and there is no option to revert back to the previous way. Why some Software companies keep thinking that users have to spend all their time on their software by clicking unnecessary buttons is beyond me.

@Per Lundstrm The extension doesn't seem to do anything... Windows/Chrome here - cleared cache, restarted Chrome, checked the extension is active but I see no difference. Also, the permissions appears pretty scary from a security perspective so I de-installed it.

When we select a quick filter (by a simple click) we would like that previously selected filters becomes unselected by default. The issue is that most of time we need to activate one filter at the same time, so we are forced to unselect manually previous filters one by one. We could enhance the selection functionality to combine several filters together (actual behavior), only by holding the CTRL button while selecting a new filter.

We need to use quick transformation filters that behave as if they are connected with an "OR" instead of an "AND" clause. I realize doing that would be problematic, but there would be a simple workaround if it were possible to merely invert the effect of selecting the filter buttons. Specifically, when the button is deselected (the default state) the filter would be applied, and when selected the filter would be deactivated.

This could be implemented by providing a single checkbox in the edit screen for a quick filter that inverts the effect of the filter. So instead of not showing non-matching items, selecting the button would now show non-matching items. This may sound confusing at first, but only the creators of the filter buttons need to understand the logic. Most users would just see a button that says "include x" or something to that extent and know that selecting it shows "x" which was filtered out by default.

When such a filter is created, it would be written according to its default (button deselected) behavior so that it filters out the items that selecting the button are intended to show. However, it should be named according to its deactivated (button selected) behavior so that users know its effect is to include rather than hide certain items.

As an example, let's say that I have a number of possible statuses for each issue, and I want buttons for each status that when selected show all issues having that status. As it stands, the only options are (1) have the buttons filter out every other status besides the desired one or (2) design the buttons to hide all issues with a given status. The obvious problem with (1) is that selecting more than one button returns nothing. The problem with (2) is that it is cumbersome to select every single status that one wishes to hide, just to show one or two of them.

If it were possible to simply invert the effect of the "hide" buttons in method (2), then by default (when deselected) these filters would all be active, showing none of those statuses. The buttons would obviously be renamed as "show x" rather than "hide" so users know to select the desired subset of statuses, instead of the undesired subset.

All of your personal information, including email address, name, and IP address will be deleted from this site. Any feedback you have provided that others have supported will be attributed to "Anonymous". All of your ideas without support will be deleted.

The alternate to this is to be able to create a custom swimlane where each project is grouped together, but I don't want this setting on by default, so the quick filter option would be much better. I have tried to create the Swimlane using custom query containg the JQL "ORDER BY project ASC", but this only creates one group called Projects, not a group for each project.

The board shows issues matching the intersection of active filters, not the union, so the approach I'd suggest is to have filters of the form PROJECT != your_project_name, titled "Hide your_project_name" so that people select the filters for projects they aren't interested in, leaving the ones they are showing.

Don't think you can do that. A quick filter is literally a link - it's can't be rendered as a drop down list. And it is, as is titled, a "filter". So each filter you click the link for restricts to cards that match that filter. Quick Filter just doesn't have functionality to do what you want.

By default, the Kanban board will display all the issues that are returned from the selected filter. However, there might be times where you need to do additional filtering on top to narrow down the list of issues further. This is where quick filters come in.

Quick filters let you define additional filtering based on JQL. This is like creating a custom view for the board to include only the issues that you are interested in seeing for the time being. To create new quick filters, perform the following steps:

With Filter Epics toggled in the Filters drawer, click on the Components dropdown. The dropdown will display all the components from your Jira project. Select the component/s you would like to filter your epics on the Story Map by. Only epics with the selected component/s will be displayed on the Story Map.

With Filter Epics toggled in the Filters drawer, click on the Quick Filters dropdown. The dropdown will display all of the quick filters from your Jira board. Select the quick filter/s you would like to filter your epics on the Story Map by. Only epics that match the conditions of your selected quick filter/s will be displayed on the Story Map.

With Filter Epics toggled in the Filters drawer, click on the Assignees dropdown. The dropdown will display all the users in your Jira instance. Either search by text, or scroll to find and select the assignee/s you would like to filter your epics on the Story Map by. Only epics assigned to the selected users will be displayed on the Story Map.

When you have Easy Agile Personas installed in conjunction with Easy Agile User Story Maps, you will have the ability to filter your epics by Persona and Importance to Persona.

With Filter Epics toggled in the Filters drawer, click on the Personas dropdown. The dropdown will display all of the Personas created in your Jira project. Select the personas/s you would like to filter your epics on the Story Map by. Only epics with the selected persona/s will be displayed on the Story Map.

You can filter the issues in the additional hierarchy on Story Map by status category. To filter these issues by status category, click on the Filters button on the header. Ensure the filter for issue hierarchy has been selected in the Filter drawer. Navigate to the Status Category drop-down. By default, issues in the To Do and In Progress status categories will be shown, and Done issues will be hidden in the Issue Hierarchy on the Story Map. To show Done issues in the additional hierarchy layer, click on the dropdown and select Done.

3a8082e126