How to merge the measure of same name components together?

Hi,
We have created like 10 projects in JSM for now and each of the projects has 5 types of components that share the same name. But when we trying to make a report choosing those components on row the reports which we were able to get is based on 55 types of component(No component Included).
But we only want only those 5 Names to be seen but they should contain all the issues from every project.

For reference, Kindly look into the attached Screenshot below.


.
So, Is there any way that we can club all the issues of Aumina Analytics together with just one Aumina Analytics row?

1 Like

Hi @Imvikrant03,

Since your components are from different projects, their full mdx name are probably different. Something like:

[Project].[Project1].[Aumina Analytics]
[Project].[Project2].[Aumina Analytics]…

You could create a calculated member that is the aggregate of all those components

Aggregate({
[Project].[Project1].[Aumina Analytics],
[Project].[Project2].[Aumina Analytics],
[Project].[Project3].[Aumina Analytics],
[Project].[Project4].[Aumina Analytics],
[Project].[Project5].[Aumina Analytics]
})

This will create a new member that includes all issues from the Aumina Analytics components from all 5 projects, but will still be drillable to see independently.
If you don’t want it to be drillable at all, you can use a SUM instead of aggregate.

Hope this helps a bit,
Have a good day,
Marilou

2 Likes

Hi @Imvikrant03

Welcome to eazyBI community.
Apart from the comment from Marilou, you could also try using Javascript in advanced settings to define a new calculated field “Component” and import it as separate dimension.
Here is the code example:
https://docs.eazybi.com/eazybijira/data-import/custom-fields/javascript-calculated-custom-fields#JavaScriptcalculatedcustomfields-Component

And here is a similar community post about it:

@Marilou thanks for the good suggestion

Martins / eazyBI support

1 Like

Thanks, martins,
It’s working like a charm. :slight_smile:

Hi Marilou,

Thanks for your suggestions, for a similar requirement we have gone through with the same method and it’s working fine while we have created another dimension for the component with the help of javascript.
So, Yes, this is also a correct solution. :slight_smile: