It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

EazyBI - group issues by tags & JQL Query Edited



I have my graph, that shows the evolution of hours for an Epic chosen:


As you can see in this image, the dimensions I have are

  • Measures in columns
  • Time in Rows
  • Issue Type and Issue in Pages.

Okay. So the problem is that the Epics I can chose is the dropdown are too many.

I want to have only Epics that original estimated hours > 20.

I tried to put a JQL Query in Source Data: 

project = myProject AND issuetype = Epic AND originalEstimate > 20 AND status not in (Abandoned, Done)

The filter work, but now the hours spent doesn't work anymore:


Can you help me, please ?


Furthermore, can I have a dropdown list that allows me to have a grouping of hours by tag, or label for exemple ?

--> Like the dropdown with Epics to chose, can I have a dropdown with Tags to chose, that shows the sum of Epics with this tag ?


Thank you :)




2 answers

... Any suggestion ?

Thank you



In this case, you could try the following approach.

At first, you could define a new Javascript calculated cusotm field via eazyBI advanced settings using the following code:


name = "Epic with more than 20 hours estimated"
data_type = "string"
javascript_code = '''
var chara =;
var charb = issue.fields.timeoriginalestimate;
if(charb > 20 && chara == "Epic")
issue.fields.customfield_epor20 = 1;

Next, you could open eazyBI import settings and select to import your new custom field "Epic with more than 20 hours estimated" as property.

In the same step, you could ensure that "Epic Link" is imported both as dimension and property (I believe this part should be already covered in your account since you use Epics but anyway..)

Later you could create a new calculated member in "Epic Link" dimension using the following code:


    [Epic Link].[Epic Link].Members,
    not IsEmpty([Epic Link].CurrentMember.get('Epic with more than 20 hours estimated'))


Next, you could use "Epic Link" dimension (where you select your new calculated member) in your report pages as the filter and then "Issue Type" dimension is not needed anymore.


Epic link dimension with member which checks imported property.png


Without "Issue Type" dimension your report should execute faster.

Let me know if that can be an option for you.


Martins / eazyBI support

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted in Jira

Calling all Jira Cloud users! Give us feedback on our exploration of a new navigation.

Hi everyone! My name’s Matt and I’m a product manager at Atlassian. I work in the navigation & findability space for all our Jira Cloud products. We’ve been working on trying to improve the exp...

959 views 15 12
Join discussion

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you