Hello @Behzad_Nazarbakhsh
Thanks for the follow-up. It looks like the report may be overcomplicated.
You mentioned you are using the parent-child relation, but in one of the measures you shared today I am noticing that you are descending from the Standard Issue hierarchy. In fact, if you use the Issue Hierarchy, the iteration through Issue dimension would not be needed.
Based on your response, it is still not clear if the hierarchy is imported into eazyBI, you mentioned what you use in Jira, however, you should make sure that the hierarchy also shows up in eazyBI. Depending on whether you use Cloud or Data Center the set up is slightly different. But you should make sure that the Parent Link is selected for import. Please check out the documentation page here- Plans custom fields
Here is a screenshot from my test instance. Let’s assume your OCM Epic is my Epic level. When you expand the Issues dimension and you have imported your Parent Link, you should see the Parent hierarchy. If you select on any level, you will see the issues from that particular level and with measure “Issues created” you will see how many issues are under these issues - in my case - under each Epic.
If you require ti have Projects in Rows and Epics in Columns, move the Issue dimension to Columns but stay in the required hierarchy
For example purposes, I will only focus on 4 Epics
Since you don’t want to see all Issues created in particular OCM Epics, but rather OCM Tasks with particular statuses, you should then use different measures by using the Tuple functions
For example, this measure will return the count of OCM Tasks within the OCM Epics with Status Done.
(
[Measures].[Issues created],
[Issue Type].[OCM Task],
[Status].[Done]
)
Your goal is to return the percentage of Done OCM Tasks, in that case, use the measure below
(
[Measures].[Issues created],
[Issue Type].[OCM Task],
[Status].[Done]
)
/
(
[Measures].[Issues created],
[Issue Type].[OCM Task],
[Status].CurrentHierarchy.Defaultmember
)
Here’s how my report looks with the calculation above
Another observation I have made from the measures you shared is that you mentioned that “selected in activity” field is a checkbox field. In the formula, you use a > 0. Your checkbox field will return a value - such as “Yes” and will not work with > operator, because your value is not an integer. If you are only interested for issues that have been set to “Yes” in this field “Selected for Development” then drag this dimension to Page Filters and filter your report by value “Yes”
See example below:
If you want to incorporate Selected in Activity" logic directly in the measure (rather than as a page filter), you can adjust the measure accordingly, by adding another layer in the Tuple function, like this
(
[Measures].[Issues created],
[Issue Type].[OCM Task],
[Selected in Activity].[Yes],
[Status].[Done]
)
/
(
[Measures].[Issues created],
[Issue Type].[OCM Task],
[Selected in Activity].[Yes],
[Status].CurrentHierarchy.Defaultmember
)
Best wishes,
Elita from support@eazybi.com