We have been observing this peculiar behaviour over the last few months.
The data shown on dashboard charts are not correct even though the JQL used for the same charts gives correct data
The dashboard shows a huge count, which is annoying
Hi @Chinmaya Panda ,
Welcome to the community!
There are lots of filtering options and configurations you can do to a dashboard.
Can you explain what filters and gadgets you are using, what you want to achieve and please add some screenshots of your dashboards and filters.
best regards
Lisa
I'm using native JIRA two-dimensional charts
The total number of issues here is 79, but when I click on the 79 to see the details
JIRA will open up the saved filter which was used for this chart
Below shown is the configuration of the chart as shown below.
However if I execute the saved filter the output is not 79, it's just 50, as shown below.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Intriguing! Just as John wants below I'd like to see the full filter JQL
What happens if you click on the totals - 61 for CAMworks and 18 for Nesting works => what numbers of tickets will you get when viewing those "subfilters" in issue navigator?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Lisa Forstberg It used to work properly for many years when we click on 61 for CAMWorks it used to show the correct query with the filter applied
But it has stopped working for the last few months
Just for your information below is what I clicked on 61 for CAMWorks
and when I click on 18 for NestingWorks
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Intriguing.
Seems like you cant see the Nesting works tickets at all and some of the CAMWorks tickets are hidden. If you go to the nesting works project, are you allowed to browse this project at all? Are there any issue security schemes applied to these projects.
I would however expect that the dashboard gadget would only present those tickets that you have browse permission to.
What kind of field is the "Rework" field? is it a single select or multiselect field?
What happens if you copy the filter and remove the resolution - condition and use the filter in the dashboard? Is it still displaying the wrong numbers?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
There are no issues related to permission as I'm the project admin in most of the projects.
Rework is a dropdown list with a single selection option
I figured out that if I remove the rework field from JQL or wherever this field is not used it's working properly.
Not sure what has changed in the last few months that is affecting
One change I fairly remember previously when I used to write JQL previously it used to Rework changed to "Rework[Dropdown]" recently
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Chinmaya - Welcome to the Atlassian Community!
Can you share some screenshots that show the differences?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Can you share the entire filter?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@John Funk & @Lisa Forstberg This is a simple filter and we have been using this functionality for a long while, we have observed this weird behaviour recently (maybe in the past 3-4 months)
somehow the forum is restricting me from posting the query in text here, so putting the image
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
It seems like the Rework field is the difference. If you take that part of the query out, do you get the same numbers as in the gadget?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Just observed the problem is with the charts where the "Rework" field is used, but not sure what has happened or changed recently these dashboards and JQLs used to work for so many years and stopped working or behaving weird all of a sudden
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Okay, I figured as much. What is the actual filter that is being used by the gadget?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@John Funk As I wrote previously the filter the JQL contains "Rework", we have not changed it in the last 2 years (if I remember correctly), what I tried to check is after removing the "rework" temporarily and the values I got were correct
I checked a few other cases where we had JQL without this field, there the results were correct.
Now I'm clueless as to why this has changed
As I get different results for the same filter with different dashboard gadgets
With Jira native Two dimensional filter statistics [Wrong]
With Jira native pie chart [Wrong]
With Jira native Filter result [Correct]
Using addon charts [Correct]
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
What type of field is the Rework field? Is it a single pick list?
And again, can you share the actual filter used by the filter? Not the results filter when you click on a value, but the actual filter.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes "Rework" is a single pick list
I have shared the actual filter earlier as well unfortunately when I try to put the entire filter here it does not allow me to post so providing the image
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Since you only have one value, you might try updating the filter to use = instead of in. That's probably why you are getting the "Irrelevant" option in the pie chart, and probably why the counts are inflated.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You should contact Atlassian Support then and see what they say.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Spend the day sharpening your skills in Atlassian Cloud Organization Admin or Jira Administration, then take the exam onsite. Already ready? Take one - or more - of 12 different certification exams while you’re in Anaheim at Team' 25.
Learn more
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.