nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

JIRA Pie Chart Gadget Displays Mutiple Entries for Single Custom Field

Gary Pasquale

Hi,

I've configured the Pie Chart gadget in JIRA to use a very simple JQL query (like the one below)

project = "Project A" AND "Custom Field A" = Yes

However, when displaying via the Pie Chart gadget on a dashboard splits the results in to 2 entries. Both called 'Yes'.

The total of both entries are the same as the total returned in the JQL query. So all Issues are being displayed on the gadget, but for some unknown reason the gadget is splitting them up.

If I select one of the dashboard entries to take me back to the Issues in the Issue Navigator, the number of Issues found remains the same but the query has changed to:

project = "Project A" AND "Custom Field A" = Yes AND "Custom Field A" = Yes

Has anyone seen this before? Any idea why this would be happening?

Thanks in advance for you help.

Gary.

Screen Shot 2017-03-03 at 9.02.25 AM.png

Screen Shot 2017-02-22 at 4.13.21 PM.png

Accepted answers

All comments

Nic Brough -Adaptavist-

I assume the pie chart is reporting on the custom field? Do you have two entries for "yes"?

Gary Pasquale

No. The context on this Custom Field only has 3 values.

Yes

Self service

My JQL query is just looking for the value 'Yes' on Project A.

Nic Brough -Adaptavist-

Ok, and what is the statistic type?

Juan Manuel Herrera

I have similar issue and this is something happening for a field that have more than 5 contexts for different projects - My pie chart gadget shows duplicates for same vale something like below

My value 6

My value 4

other values 1

So if I hit the link for the for the filter this actually shows a total of 10 for "My value". So the issue is only on the representation for the pie chart.

Thanks

MattS

Do you have two custom fields with the same name being used in the screens of that project?

Scott McDonald_qykakt

No and I even confirmed no other field is using that fieldID

PD Sheehan

What I think @Nic Brough [Adaptavist] is trying to get at is that each custom field can have multiple contexts (for defining different option values for specific projects and issue type).

If a custom field has 2 or more context configuration with identical option values, the pie chart gadget will group on the underlying id of each option, not the option's display value or label. I think this is probably an incorrect design.

For example, from my custom fields screen, I click on the cog for my field and select "Configure".

I have 2 different context with the same values. Overlayed on the image, I've added the option value id as stored in the database to demonstrate the the values are different.

image2017-3-16 10:14:53.png

The solution is to either get unique values in your two contexts, or consider merging the two contexts. Note that this is not trivial as after you delete the context, all issues that had values defined will lose those values and will have to be re-applied. A groovy script could be generated to do that but it would be a little conplex.

image2017-3-16 10:14:53.png

Nic Brough -Adaptavist-

I think we moved past that point, but you do put it very well.

Problem though - it's not a design flaw - A in context 1 is not the same as A in context 2. They're separate items that just happen to have the same name.

PD Sheehan

I think that as a user, I don't care what the underlying contexts are.

In a graphical representation and grouping, I think the grouping should be based on the displayed value. That how most BI tools I've ever used do.

Amir Katz (Outseer)

My vote is with @PD Sheehan - Sometimes, one project has 5 options and the other has only 4, but I need the names to be identical.

So I also think it's a wrong design.

What is really needed here is a checkbox that will say 'aggregate identical values across field contexts' and everyone will be happy.

From past experience, I wouldn't hold my breath on such a feature request...

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

jira-software