Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Chart is showing issues that are not part of the control "fix version"

Johanna Hurtado Morales
April 25, 2026

Hi everyone, 

I am using a chart to count (distinct) the number of stories, bugs,etc included in a specific release (Fix Version). However, when I select a Fix Version from the control, the chart shows more than 2,000 issues, including issues that do not have that Fix Version selected and even including issues with null fix version.

I expected the chart to return only the stories, bugs,etc which are only 11 issues that are explicitly associated with the selected Fix Version.

Could someone please let me know what configuration or setup I might be missing?

Thanks :)

fix version error .png

2 answers

1 accepted

1 vote
Answer accepted
Johanna Hurtado Morales
April 28, 2026

My co-worker and I found the way to do it

analytics release name.png

Arkadiusz Wroblewski
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 Champions.
April 29, 2026

@Johanna Hurtado Morales  Glad it solved. That´s most important.

0 votes
Arkadiusz Wroblewski
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 Champions.
April 25, 2026

Hello and welcome to the Community @Johanna Hurtado Morales 

Based on your screenshot, this is a query setup issue rather than a chart bug.

Since the results table already shows 2284, the KPI card is just doing its job, the data coming into it is what's actually wrong. The likely culprit is the {RELEASE_NAME} filter. Release names aren't unique across Jira, so your query is probably grabbing tickets from every project that happens to have a release with that same name.

To fix this, I'd recommend switching your control to use "Version ID"  instead of Name, or simply adding a Project filter to narrow things down. If you want to see exactly where those extra tickets are coming from, add "Project Key" and "Version ID" as columns to your result table temporarily. You can also peek at the generated SQL to see exactly how the joins are behaving. Seeing those IDs usually makes the fix pretty obvious.

Johanna Hurtado Morales
April 27, 2026

Hi @Arkadiusz Wroblewski thank you so much for your response. I checked in Jira and only 11 issues have the release name I am using, I filtered as well by the project and still bringing the same 2284 results.

Additionally, I checked the issues that were part of the result, and I can see those issues do not have any fix version that's why I was filtering as well that release name is not null.

I am going to try what you suggested to use the version id to see if that works. I think the issue is when crossing the main issue table "work item" to "Project" and "project fixed version" thanks :) 

Johanna Hurtado Morales
April 27, 2026

I just tried using the version ID still brings the same 2284 issues

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events