Hi! I'm new to using EazyBI. I am looking to create a report that shows tickets that have the component "Releases" and a subset of other components - Team Drupal, Team Edit, and Team Platform, see image below.
Right now it shows each of the components separately but I'd like to be able to drill down releases show how many tickets are Releases + Team Drupal, Team Edit, and Team Platform.
I'd like to ideally create a bar chart that can stack the 3 components.
I've tried to create a calculated member formula but it doesn't seem to work. Anyone have any advise?
eazyBI default grouping and filtering options will give you issues with any of selected component value. You would like to use two different approaches if you want to filter out issues with one component Release and then group issues with this component by a particular Team sub-component.
name = "Component"
data_type = "string"
multiple_values = true
split_by = ","
dimension = true
issue.fields.customfield_eazybicomponent = issue.fields.components;
1. Add the updated custom field definition to eazyBI advanced settings or ask Jira administrator to do this for you. eazyBI advanced settings are common for all accounts and only Jira administrators have access to the settings.
After import, you will have two dimensions with component selection. Please use Project dimension Component selection on Pages and select Release there.
Add new dimension Component to Columns. Search and bookmark members Team Drupal, Team Edit, and Team Platform. Select those members for a report on Columns.
Use Time dimension as in your example on Rows.
You can switch to Bar chart and use Stacked to stack issues with team components per time.
The report will give you a count of issues with Component Release stacked by particular Team.
Here is my report example. I have Project component UP, and two sub-components Left, Right.
Daina / email@example.com
We did it by a user defined measure. With this you get the components for each Issue.
[Measures].[Issue Components] =
-- iterate through all components
[Measures].[Issues created] > 0
AND [Project].CurrentMember.Name <>'(no component)'
-- retun a listo of issue related components separated by comma
Learn how to use two new reports for next-gen projects in Jira Cloud: Cumulative flow diagram and Sprint burndown chart. Ivan Teong, Product Manager, Jira Software, demos the Cumulative ...
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