EazyBI - group issues by tags & JQL Query Edited

Hello,

 

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

image.png

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:

image.png

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 :)

 

Emile

 

2 answers

... Any suggestion ?

Thank you

Hi,

 

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:

 

[jira.customfield_epor20]
name = "Epic with more than 20 hours estimated"
data_type = "string"
javascript_code = '''
var chara = issue.fields.issuetype.name;
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:

 

Aggregate(
  Filter(
    [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 Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

3,167 views 13 19
Join discussion

Atlassian User Groups

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

Find a group

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

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot