How do Pages and Tuples interact with issues history?

Questions & Answers
,
1

Hello,

in the end I want to see the amount of Backlog items in a specific set of “Status” for the past months.

I started by creating a calculated member below “Transition Status” called “MyTStatus”:

Aggregate({
  [Transition Status].[<myfirststatus>],
  [Transition Status].[<mysecondstatus>],
 ...
})

and after that I created a report specific calculated measure “amount of items in TStatus”

(
    [Measures].[Issues history],
    [Transition Status].[MyTStatus]
)

That way it looked quite useful.

Then I added a field “Teams” as pages (every Backlog item can contain multiple values of Teams!). For me interesting is a special subset of Teams so I oncemore added a calculated field below “Teams” called “MyTeams”:

Aggregate({
[Teams].[<team1>],
[Teams].[<team2>],
[Teams].[<team3>]
})

When I select this group of Teams within the pages, then I get a lot of duplicated values in “amount of items in TStatus” (yes, a lot of items have multiple Teams!). So it seems to me, that for every single team within the aggregate the value is calculated and then the results are just summed up.
But I want as result the distinct number of Backlog items.

Any ideas or helpful insights, how eazyBI combines the calculated measure with the pages?

Thanks in advance

2

Hi,

Issues history is not a distinct count measure, so if an issue has several Teams, it is counted for each Team. The distinct count of the issues history needs a custom formula, as described in this community post: Distinct count for Issue History - #2 by roberts.cacus
Unfortunately, this formula has a high risk of performance problems, and there is no feasible workaround for that currently.

Kindly,
Janis, eazyBI

3

Hello! I am also encountering this issue. Will a distinct history count measure be added in the future? Thanks!