If you look at the measures dimension in eazyBI, there are two members "Issues resolved" and "Sub-tasks resolved". When I reported on "Issues resolved" it seemed high, so when I drilled through to Issues, it looked like sub-tasks were included in that measure.
Are sub-tasks considered to be a type of issue? It doesn't make sense to me to include them in the "Issues resolved" measure.
I just looked at creating a calculated member, but subtracting from "Issues resolved" the number of sub-tasks created or sub-tasks resolved doesn't give me the correct value either.
You are correct: all standard measures (Issues created, Issues resolved ... ) includes both standard (parent) issues and sub-tasks issues.
Measures 'Sub-tasks created', 'Sub-tasks resolved', ... count subtasks for standard issues.
To calculate measures only from standard issues, use "Issue type" dimension - move it in Pages and select only standard issue types. Then all measures would be calculated only from standard issues.
If you have a lot of issue types, you could create a calculated member in "Issue Type" dimension to retrieve all standard issue types with the following calculation:
Aggregate( Filter( [Issue Type].[Issue Type].Members, IsEmpty([Issue Type].CurrentMember.Get('Subtask')) ))
Then you could use this calculated member in Pages or when creating calculated measures.
I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...
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!
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