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?
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.
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
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!
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