You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Per the instructions:
Hint: Type $ and the variable name, then press Enter to add a new variable or to select an existing variable from a list of suggestions. The suggestions dialog shows variables already defined in this template.
This is not working in the cloud, using chrome browser.
And now when I insert new variable from the menu, I receive the following error when saving:
'Can't save changes Multiple template variables which have the same name "Country" but different parameters.'
It is the same variable with the same parameters.
Welcome to Atlassian Community! It's nice to meet you. Both issues are caused known bugs.
The error message you are running into is a result of the following bug:
There's no workaround for the first issue, but with the second one:
Editing and "saving" each of the duplicated variables will fix the issue that causes the editor to think they have different parameters, and will allow saving of the page, however, it will only allow it for that particular save.
Let me know if you have any troubles with that.
Hello @Shannon S , I understand there is bug opened in order to use template variables, use them I assume in plain text / page content.
What about widgets? If I want to reuse a variable value in JQL in order to display a list of JIRA issues, am I supposed to type $myvariable in JQL edit field and it will ok once I create my page using this template?
My apologies. I had not seen your question earlier. The use of variables in JQL would be a better question for the Jira team, but I noticed they have a feature request for that within Jira:
With the ability to create and use variables in JQL searches, you would theoretically be able to save it with a filter for use in your Jira widgets. There was also a conversation about using ScriptRunner with JQL instead of variables, Is there a way to use variables in JQL? It might help.
I would recommend raising a new question in the Jira collection since those users might be more familiar with JQL and have an alternative suggestion. You can also try the Atlassian Developer Community if you are interested in some programmatic solutions. I hope this helps!
Thank you, and take care.
Thank you for your question!
It's still possible to insert new variables by clicking the + > New Variable option in your template menu. The bug affects inserting existing variables or using the $ shortcut.
You can also contact the Cloud support team and they can take a look at your site and see if it's possible to use the legacy template editor or enable it for you.
Regarding the priority, it's in our backlog right now, so that priority can change at any time depending on the factors explained in our Cloud platform bug fixing policy. Please make sure to vote on that bug so we know how many users are affected!
Let me know if you have any questions about that, and I'll be happy to help.
No, unfortunately, at this time, it won't be possible to re-use existing variables in the new template editor. The workaround mentioned in the other bug I shared (CONFCLOUD-67845) states that you'd have to save it each time you re-use a variable name.
In the meantime, please ask the Support Team to help you with accessing the legacy template editor so you don't lose this feature.
This appears to have been addressed. I can create a template, and create variables, and reuse the variables (either copy/paste) or just typing // New Variable and giving it the same name and type.
However, there's almost nothing I can do with a variable now. I can't use it in a URL, in a code snippet, in a title, in a Jira query widget... I can just include it in a paragraph.
Maybe not a lot of people use template variables these days, but I'm hoping to avoid having to build pages via the API.