Remove duplicate tickets

Hi Team,

I need your help in removing the duplicate tickets. We’re using components to identify the issues. However, sometimes, we’re using multiple components on the same ticket.
Let’s say that I want to build a report for hardware and non-hardware components.

  • If I use the component dimension as a filter and select every component individually- I get duplicates because the calculation is not made for tickets but for components.
    -if I use another dimension ( component flat - created by me) it is too much manual work because we need to select all the HW and Non-Hw components combination.
  • the 3rd option I was thinking of is components aggregation ( which we already have in place ). However, even in this case, we have duplicates.

can you suggest the best solution to fix it?

Hi @Dorina_Ababii
This is a well known challenge with multi-value fields as filters.
There is no great rules to teach reporting tool which is the most important (of many) value when multiple values are used on the issue in the field. Therefore, reporting tools tend to count the issue by each value. We usually recommend avoiding multi-value fields as much as possible - for reporting purposes.

The answer to your question depends on the report definition - what measures do you calculate and what is the layout of the report.

There are some distinct measures you can use (for example, “Issue created count”, “issue resolved count” and a couple more) to count the issue just once per report, but the list of distinct measures is very short. You can search them by suffix “…count” in the “Measures”.

Another way would be creating calculated measures to iterate through Issue dimension members and count each just once, but that would often end with timeouts as these calculations have complex iteration steps and it takes time to calculate them.

Or you could import the “flat” dimension from the field, but it comes with consequences (manual work to combine the right set of members).

Another solution would be to precalculate a field using Javascript in eazyBI advanced settings and extract just one value per field per issue and then import the field as a separate (single-select) dimension for calculations.

Martins / eazyBI