Filter variables?

[Chuck Oleary]

I searched for "filter variables" but could not find what I was looking for.

I have many dashboard and over 10 pages of filters.  Is there an easy way to create and maintain variables? 
For example teams are working on "PI Plan 2023.6" and soon will start "PI Plan 2023.7" and then "PI Plan 2024.1" etc.  

So I might have a filter like "("PI Plan[Select List (multiple choices)]" = 2023.6 OR "PI Commit[Select List (multiple choices)]" = 2023.6) AND "Team[Team]" = 4 "

This means I have to update dozens of filters ever 6 weeks.
It would be great to be able to set these for filters and quick filters on the boards.

[Marlene Kegel - codefortynine]

Hi @Chuck Oleary,

I am Marlene from codefortynine.

With our app Quick Filters for Jira Dashboards you can create "Quick Filters" on your dashboard, to filter the dashboard gadgets dynamically. 

You can read more about the filters you can create, in our documentation. 

Or you test our app, without installation on our demo dashboards.

[Jack Brickey]

Hi Chuck, natively Jira does not support dynamic filters/variables in Dashboards. There are addon apps that might meet your requirements so you May wish to check the marketplace if that is an option for you. Having said that, I'm trying to really better understand your need to see if there might be an alternative solution. In the end, though, it may mean that you have to edit your filters on a regular basis.

[Chuck Oleary]

Thanks Jack.

What I envision is Jira configuration page for creating variables, for example:

Then I could create queries like this:

"("PI Plan[Select List (multiple choices)]" = "Future PI" OR "PI Commit[Select List (multiple choices)]" = "Current PI") AND "Team[Team]" = 4 "

As it works now I have 8 teams, over 100 different queries, and every 6 weeks I need to update them all to update the PI Plan and PI Commit values.

Hope this all makes sense.  I'll also see if I can send this Jira enhancement suggestion to Atlassian.

[Bill Sheboy]

Hi @Chuck Oleary 

Adding to Jack's suggestions...You note having over 100 different saved filters and need to update every 6 weeks.

First thing, have you considered isolating the parts needing change in fewer filters so only one filter needs to change?  For example...

"PI Selection Filter", which is saved with an id, such as 123456

("PI Plan[Select List (multiple choices)]" = 2023.6
  OR "PI Commit[Select List (multiple choices)]" = 2023.6)

And many other filters use that one like this...

filter = 123456 AND "Team[Team]" = 4

filter = 123456 AND "Team[Team]" = 5

and so forth

Thus only the first filter needs to change every 6 weeks.

Next, do your filters change in a predictable manner, regarding the program increment (PI) information?  If so (and you do not want to manually change that one filter from above), you could create an automation for Jira rule with a scheduled trigger to edit the filter by calling a REST API function.

Kind regards,
Bill

[Chuck Oleary]

Hi Bill,

Stacking the filters does cut down on managing filter updates. it can turn 100+ down to a more manageable 25 or so.  That's what I do now.
I was looking for an easier way to do this.

Best regards,
Chuck