Earn badges and make progress
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
Next: Root
1 badge earned
Participate in fun challenges
Challenges come and go, but your rewards stay with you. Do more to earn more!
Gift kudos to your peers
What goes around comes around! Share the love by gifting kudos to your peers.
Rise up in the ranks
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Come for the products,
stay for the community
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
How to work around Two-Dimensional chart JQL query with field name global translation?
In our Jira environment, we use the SAFe EPIC to Feature Translator for Jira add-on. This applies a global translation to associated field names. E.g., 'Epic Link' becomes 'Feature Link'.
When using the Two-Dimensional Filter Statistics macro from the Confluence Tables and Filters add-on to report issues without a 'Feature Link', the JQL query used is simple enough that this works for the most part.
The following is the JQL query used for the filter, which is simple by itself:
However, the column entry links result in what Jira considers to be a 'complex' query requiring use of the original field name (i.e., 'Epic Link').
If one replaces the JQL query generated by the macro to use the original field name ('Epic Link') instead of the translation ('Feature Link'), the query works as expected.
- Is it possible for the add-on to understand it is generating a complex JQL query and substitute the original field name? This would presumably require looking up global translations.
- If not, are there any suggested workarounds for this issue? E.g., create a scripted custom field that mirrors the field of interest, but avoids the translation issue (which is not ideal).
Thanks in advance!
--Mike