Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

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


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.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Jira Issue Keys in EazyBI Table Matrix

Hello all. I am trying to make an EazyBI report very similar to the one found in the below community question, but I'm showing issue Components in the report rows and Labels in the columns:

However, instead of showing the Issues Created count in the table, I want to show the Jira Issue Key(s).

I have created a new calculated measure for the issue keys as


but, when I use that calculated measure, the entire table fills with zeros (0). If I add the Issue dimension to my report rows, so my Jira issues are shown in the rows, then the entire table is filled with the Issue Keys rather than only the cells that cross-reference the appropriate component and label for the issue's data.


Am I using the wrong calculated measure syntax to accomplish what I want or is EazyBI not able to display exactly what I'm looking for?

1 answer

1 accepted

0 votes
Answer accepted
Gerda Grantiņa
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Sep 16, 2022

Hi @Adam Schordine ,
Yes, this is expected behavior that issue property ([Issue].CurrentHierarchyMember.Key) is shown in the report only when the Issue itself is visible. If you want to see the issues behind the number, I highly recommend using the option "Drill through issues":
 There is an option to create a calculated member using Generate() function, but the end result can be a report with poor performance as you need to iterate through all issues. And the end result can be hard to overview as there can be an unknown amount of issue keys per cell. 


Gerda //

Thank you very much for the explanation, Gerda. I appreciate you taking the time to reply.

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events