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.
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.
The field (lets call it Field A) is a Select List (single choice) with 4 contexts to choose from - public, internal, sensitive, restricted. When I add a pie graph to a dashboard and select my project the statistic type of "Field A", I have 'restricted' appearing twice. I then will click on restricted and it brings me to a filter (which seems basic) of project = project A and field A = restricted. One thing I did notice is the restricted value that appears twice each have a different color assigned to them.
Yes, for example, one of the "restricted" values in the graph displays the number 14 and there's a second "restricted" that displays the number 4. When I click on both of the "restricted" text, it displays 18 total issues. Attached is the list of my custom field section. Is there a different section you're looking for?
Screen Shot 2017-03-03 at 9.02.25 AM.png
We need to see a screenshot of the custom field section that includes the field you're struggling with and to know the issue type. None of the text stuff though - I imagine knowing that vendor "dave" is "restricted" might be sensitive, but if you don't show us "dave", just the classification field, it should be ok.
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.
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.
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs