The Pie chart is showing duplicate values or options on Jira dashboards
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
Pie charts can be added to Jira dashboards and used to report on issue status, priority, assignee, components, custom fields and more. Under some conditions, duplicate values might be visible on a pie chart. This knowledge article lists the most common root causes for this issue.
Environment
Jira Server/Data Center 8.0.0 and any higher version.
Cause
Root Cause 1 - the field used by the pie chart is the component field and has duplicate values across projects
If different projects are configured with the same components, and if the Pie Chart is not limited to 1 project only, the duplicate components will not be combined together. Instead, they will be treated as different components. As a result, the Pie Chart will show duplicate components as shown in the screenshot below:
This behavior is due a limitation with the Pie Chart functionality. There is a public feature request meant to change this behavior by combining all the duplicate components, which is linked below:
Root Cause 2 - the field used by the pie chart is a custom field and has multiple context configurations
Custom Fields can be configured with different context configurations associated to different Jira project and issue types. In each context configuration, different default values and options can be configured for custom fields of type "Select List (single choice)" or "Select List (multiple choices)".
If a custom field is configured with multiple contexts, and if different contexts are configured with the same options (as shown in the screenshot below) these options will be treated as duplicate values by the Pie Chart.
This is what the Pie Chart will look like based on the example of Context Configuration shown above:
This behavior is tracked in the public bug ticket linked below:
Solution
To prevent the Pie Chart from showing duplicate values (and regardless of the root cause), it is necessary to modify the filter configured with the Pie Chart, so that only 1 specific project is involved. You will need to configure as many filters (and Pie Chart Gadgets) as projects for which you need to get a report of a specific field.
Was this helpful?