Is there a way to use variables in JQL?

I would like to create a set of queries for a dashboard that I can re-use from version to version such that I can use a variable in the JQL.  This would allow me to make a single change which would affect all the filters used on that dashboard.  The only other option is to manually edit every bloody filter.

3 answers

1 accepted

2 votes

I would have suggested using ScriptRunner to programatically update the JQL queries. I've done this before and it worked well, it's not particularly difficult. But you discounted that plugin, so I have another suggestion.

Create a shared filter named FixVersionFilter as:

fixVersion = 'big branch' and status = Open

Then you create your project filters as:

project = dookie and filter = FixVersionFilter

Then when you change FixVersionFilter it will affect the results of the project-specific filters.

That looks like it would work! I had no idea you could filter on a filter. Where's Xzibit when you need him?

You can't use variables out of the box, no.

Scriptrunner allows you to use additional JQL functions or to make your own. For instance, you could create your own latestUnreleasedVersion() function that would always return, hum, the latest unreleased version.

Check out the documentation.

I'm hesitant to use ScriptRunner now that they have moved to a pay model.

Yeah, but to be honest, that plugin was way too good to be free. It's really worth the cost, especially the regex match functions (componentMatch, projectMatch)

Perhaps, but even so, I'm likely not going to get additional funding for paid plugins. Using it could mean we would never be able to go past Jira 6.

The other thing is I would need to teach myself how to use it from the ground up. I can't really justify asking for funds for a plugin I cannot use.

I hear you. I always have hard choices to do with limited budgets too. I really doubt you'll be able to fix your filter issue for free. Creating your own plugin is possible of course, but unless you're already pretty good at it, there's no way this is cost-effective.

I usually use the "fixed" statements like "startOfWeek()" "startOfMonth()" etc... so the values are not static and updates automatically, that's the closest you can get with this I think. Since filters in the dashboard is dependent with Gadgets, this will make your feature request tricky. Where to put those variables then? You can send a request to Atlassian and see what they think about it. There maybe an add-on for it or a gadget add-on though...

I probably will enter or vote on a request, but let's be realistic. Atlassian still hasn't implemented WYSIWYG, the ability to rename groups, subcomponents, etc... some of these request are teenagers. By the time my request gets done I'll likely be retired. The pre-fab variables are OK for some things, but they don't help. We work on multiple versions simultaneously, along separate branches. I need a variable per branch to show the current state of the branch. I would use something like: project = dookie and fixVersion = "big branch" and status = Open We don't actually have a dookie project, btw

We are in the same situation. We have a dashboard per major release that needs to be manually recreated each time.

Suggest an answer

Log in or Join to answer
Community showcase
Teodora [Botron]
Published Feb 15, 2018 in Marketplace Apps

Jira Inferno: The Nine Circles of Jira Administration Hell

If you spend enough time as a Jira admin - whether you are managing a single, mid-sized instance, a large enterprise one or juggling multiple instances at once - you will eventually find yourself in ...

1,197 views 6 19
Read article

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
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot