Duplicates custom fields in Pie chart report

Sofia Quintero
Contributor
July 27, 2020

The report shows me duplicate each of the values of a custom field. 

It´s represent a few projects with the same context for the custom field in one issue type

What could be the cause? And how can be fixed?

 

 

 

Problema campo severidad.png

3 answers

2 accepted

2 votes
Answer accepted
Tom Harris - Old Street
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
August 2, 2020

Hi @Sofia Quintero ,

I noticed the same issue when I was using Next Gen projects so we added a feature to our app Custom Charts for Jira that merges values that have the same names.

You can see it helps for statuses in this example, but also works well for priority and all other field types :)

Duplicate Statuses.jpg

The app also has a lot of other features that could be useful like the ability to select the colors and order of the segments. It also comes with a wide range of chart types. You can test it out here on our interactive app playground.

I hope that helps!

Tom - Custom Charts Product Manager

Sofia Quintero
Contributor
August 3, 2020
Like # people like this
0 votes
Answer accepted
Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
July 27, 2020

Hi @Sofia Quintero 

When you examine your JQL that you use for this gadget, are the values actually the identical for the custom field, or slightly different (e.g. extra spaces)?  You can check that by running the JQL separately in issues and filters and comparing the results.

Best regards,

Bill

Sofia Quintero
Contributor
July 27, 2020

Hi @Bill Sheboy I use the custom field in the "Statistic Type" of the gadget, no in the jql query

Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
July 27, 2020

Thanks for that information, Sofia.  

How do you select the issues for that gadget: with just one project or with a query?

However you do this, I was suggesting using that same selection criteria to check if the values of the custom field are indeed identical, or not.  (e.g. "Low" vs "Low ")

Sofia Quintero
Contributor
July 27, 2020

@Bill Sheboy  

I select the issues fot he gadget by a JQL query that includes a few projects. 

Let me try your search suggested

Like Bill Sheboy likes this
Sofia Quintero
Contributor
July 28, 2020

@Bill Sheboy 

 

I compared the results with the jql search with each Values ​​of the custom field.
When i searched for "Low" it returned the same count than the sum of the duplicate fields on the gadget.

Sofia Quintero
Contributor
July 28, 2020

Also, an other detail to mencioned it´s that: the custom field had 3 context. New one was created and the involved projects were move to this one, and one value of the others contexts wasn´t include in this.


After that became to appear the duplicates values on the gadgets

The query doesn´t contain projects of other contexts, just the involved projects of the "New context created"

Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
July 28, 2020

Hi @Sofia Quintero 

I searched the public open tickets on this issue and I could not find anything similar to context change causing this symptom.  As this does not appear to be status related (which is a known Classic/Next-Gen project "behavior" in duplication of values), I recommend contacting Atlassian to submit a defect here:

https://support.atlassian.com/contact/#/

Sofia Quintero
Contributor
July 29, 2020

@Bill Sheboy  you were right, it seems to be a Bug  when: a custom field with multiple context is used on Statistic Type of a Pie chart report.

Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
July 29, 2020

Thanks for finding that one, @Sofia Quintero   Although I am surprised it is marked as minor...One of the primary purposes of a tool such as JIRA is to store information, and this defect seems to impair the validity of and access to the stored information.

The defect you linked is for the server version, and you are using Cloud, correct?  If so, please let support know so that they can amend/clone the defect to cover the Cloud version also.  Thank you!

Like Sofia Quintero likes this
Sofia Quintero
Contributor
July 29, 2020

@Bill Sheboy I don´t have the permission to clone, what should i do?

Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
July 29, 2020

Hi!  As you are the site admin for a Standard Cloud instance, you can submit a support defect ticket using this link:  https://support.atlassian.com/contact/#/

You can provide the other server defect ID, and ask if they want to fix the issue, clone the original ticket for cloud, or create a new one.  Then you will get updates as they work the ticket and they have visibility that this is a cloud issue also.

Sofia Quintero
Contributor
July 29, 2020

@Bill Sheboy Thank you very much for all the support!

Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
July 29, 2020

Glad to help.  When you hear back from support, please post back here if there are any updates... although, the other defect is 3 years old  ;^)

Please consider marking this one as answered so others in the community searching can find that there is an open defect on this symptom.  Thanks!

Like Sofia Quintero likes this
1 vote
Italo Qualisoni [e-Core]
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
July 27, 2020

Is your JQL looking for Next Gen projects ? This could be the reason since each project will have its own options and even with the same name their options would be different for each project.

Sofia Quintero
Contributor
July 28, 2020

@Italo Qualisoni [e-Core]Sorry what do you mean with "Next Gen projects"?

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events