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
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.
Thanks in advance!