The component is a multi-selection field in Jira, and each issue may have more than one.
To get related components to the issue, you may use function Generate() and iterate through all components which are related to issue. A formula may look like this:
Generate(
-- iterate through all components
Filter(
[Project].[Component].Members,
[Measures].[Issues created] > 0),
-- retun a listo of issue related components separated by comma
[Project].CurrentMember.Name,
', ')
Another approach is to import Component as issue property in eazyBI. To do this, you may define Component as JavaScript calculated custom field.
In eazyBI advanced settings, copy in this definition with JavaScript to fetch issue component.
I understand that you have JavaScript to import component as issue property and represent it for each issues. Data re-import does not change selected projects and custom fields in eazyBI import options, but sometimes users deselect some of the custom fields. Go to import options, tab Custom fields, and check whether “Component” is selected for data import.
When Component is imported as issue property, you will find it in Measures -> Issue properties -> Issue Component.
Thanks for the update: When I try that I get the following error: “Execution of custom JavaScript code raised the following error:
missing ; before statement”
Now the code looks right. Might be that the right formatting for the quotes is lost with copy paste, but otherwise than that the code is correct.
If you still have the same problem adding the code to import Component, please contact support@eazyBI.com and send them the whole advanced settings of your eazyBI environment.
Hi @zane.baranovska,
Your code worked perfectly for me to bring the components as a property of an issue. Is it possible to get the components as a dimension? We use the same components across all of our projects and I’d like to summarize data by those components.
Thanks!
Laurie
Actually @zane.baranovska,
I found it as a hierarchy level under the project dimension. I think that will do the trick!
Thanks again for your earlier post.
Laurie
Yes, Component is a separate hierarchy level in the Project dimension. If you do not have similar components across projects, then this solution works perfectly.
However, if you have the same components in several projects, then you may import Component also as a separate dimension using the same JavaScript code. In that case, add one more line to the advanced settings dimension = true to enable custom field import also as a dimension.
With this version 6.1 eazyBI has additional set of default properties Issue Components, Issue Sprints, Issue Fix versions, Issue Affects Version etc.).
Since eayBI version 6.6 and on Cloud, there is an option to create calculated fields in the account import options (without disturbing the Jira system administrator or eazyBI admin).
Now you can create a Component dimension in import options → tab Custom fields.