Maybe it’s a too dummy question but I need to bring all issues of a type when are in specific status. This is the code I’m trying but some issues are missing besides the status matches:
Is this the best approach to have a list of issues in MDX? I’ve tried to use this but won’t worked too:
([Status].[Product Backlog, Ready For Development, Blocked],
[Priority].[Low],
[Issue Type].[Bug])
Anyway it seems not considering all issues and there’s no measure in my actual code, this is what I need (but I just know how to use with Open Issues):
I think I’m closer, but still geting only the not resolved issues:
–annotations.group = Bug Backlog Measures
aggregate(
{[Status].[Product Backlog],
[Status].[Ready For Development],
[Status].[Blocked],
[Status].[In Development],
[Status].[Developed],
[Status].[Tested],
[Status].[SIT Done],
[Status].[UAT Done],
[Status].[In Business Analysis],
[Status].[In Technical Analysis],
[Status].[Approved for SIT],
[Status].[Approved for UAT]}, ([Measures].[Open issues], [Priority].[Low])
)
Yes, the tuples is the right choice to calculate the value of a measure for a specific combination of other dimensions.
We usually recommend using also the measure in the structure of a tuple.
I believe this is the right fit for your case to aggregate Low priority issues in all these statuses:
Aggregate(
{[Status].[Product Backlog],
[Status].[Ready For Development],
[Status].[Blocked],
[Status].[In Development],
[Status].[Developed],
[Status].[Tested],
[Status].[SIT Done],
[Status].[UAT Done],
[Status].[In Business Analysis],
[Status].[In Technical Analysis],
[Status].[Approved for SIT],
[Status].[Approved for UAT]}, ([Measures].[Issues created], [Priority].[Low])
)
But I wouldn’t recommend creating a measure where you count “Issues created” + “Issues resolved” as the second set of issues could also belong to the first set if the issue is resolved.
Anyway, great that you find a few ways to create calculated measures in your report.
Hey @martins.vanags many thanks for your reply. I’ve changed the way you recommended and it’s working, the problem you levered wasn’t visible in the test scenario but sure would happen so let’s follow the good practices
