Hi @Timi
What you are experiencing is actually the expected behavior of multi-choice fields like Environments (or Labels, Components, Fix Version) in eazyBI. When a field can hold multiple values per issue, eazyBI counts that issue once for each matching value. So if a single ticket has 3 environments, it will contribute to all 3 environment columns, this is by design, as eazyBI categorizes and aggregates data per dimension member.
There are two approaches to solve this:
Option 1: Import Environments as a CSV dimension (recommended for performance)
This allows you to analyze issues by their combination of environment values rather than by each individual value. Each unique combination (e.g., “Env A, Env B”) becomes a single dimension member, so an issue is counted only once.
In import options, edit the advanced settings for the Environment field; add parameter
csv_dimension = true. During the next import, eazyBI will create a new dimension “Environment CSV” which you can use for filtering and grouping data.
See this community post for more details on a similar use case:
Option 2: Calculated measure to count issues that were flagged.
An alternative is to create a calculated measure to count each issue only once, regardless of how many matching environments it has. The formula would look something like this:
NonZero(
Count(
Filter(
--iterate through individual issues
DescendantsSet([Issue].CurrentHierarchyMember, [Issue].[Issue]),
--issue is flagged and matches report context (selected environments and other fields)
[Measures].[Afterhours Issue Flag] > 0
)
)
)
The calculation iterates through all imported issues to check their flag and assigned environments, therefore, it may affect report performance on large datasets.
Best,
Zane / support@eazyBI.com