filters as variables!

[Bryan Collick]

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?

[Alexey Matveev · Accepted solution]

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.