Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

×
Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

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.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

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!

Leaderboard

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.

Two-Dimensional Chart Configuration.PNG

The following is the JQL query used for the filter, which is simple by itself:

JQL Filter Query.PNG

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').

Two-Dimensional Chart Example.PNG

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.

  1. 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.
  2. 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

0 answers

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events