Hi @RBL ,
I would suggest using Affects version in Rows so the second measure provided works as expected.
To get the number of issues created for both versions you can use this measure (it sums issues in affects version together with issues that have the same fix version. And to remove duplicates then subtracts issues that have same fix and affect version in one issue):
-- count of issues in selected affects version
[Measures].[Issues created]
+
-- count of all issues with the same fix version
(
[Measures].[Issues created],
[Fix Version.By name].[Name].GetMemberByKey(
[Affects Version].CurrentHierarchyMember.key
),
[Affects Version].CurrentHierarchy.DefaultMember
)
-
-- count of issues that have the same version as fix version and affects version
(
[Measures].[Issues created],
[Fix Version.By name].[Name].GetMemberByKey(
[Affects Version].CurrentHierarchyMember.key
),
[Affects Version].CurrentHierarchyMember)
For the second measure you can use the formula provided here (change expression in DateCompare() with >0 to see issues created after release date):
In the report it looks like this:
best,
Gerda // support@eazyBI.com