filters as variables!

So I came to the realization that you can kinda use JIRA query filters as basic variables. That is to say, if I regularly start my query with

project = foo AND status is EMPTY and duedate < now()

I can save this query as FOO MISSED and then build subsequent queries like

filter = "FOO MISSED" and component not in (bar, lol) and labels is not EMPTY

This was probably obvious to most but is a big gain for me. Any limitations to this? Any problem with nesting filters within filters? Anything else I should be mindful of while doing this?

1 answer

1 accepted

0 vote
Alexey Matveev Community Champion Nov 01, 2017

Hello, 

We used this feature to make our life easier when we had to write multiple similar jql queries.  We moved out the common part into a base filter and then referenced to the base filter from other jql filters. We had several levels of hierarchy and met no limitations so far. 

Suggest an answer

Log in or Sign up to answer
Atlassian Community Anniversary

Happy Anniversary, Atlassian Community!

This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.

Read more
Community showcase
Julia Dillon
Posted Apr 17, 2018 in Jira

Tell us how your team runs on Jira!

Hey Atlassian Community! Today we are launching a bunch of customer stories about the amazing work teams, like Dropbox and Twilio, are doing with Jira. You can check out the stories here. The thi...

764 views 2 19
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you