Control Chart vs JQL Filter difference in results

Question

I have been this a JQL filter to view tickets completed by one of my squads over a timeframe:

"filter = 238820 AND component != "EDS (Internal) - Cost Down Idea" AND issuetype = story AND STATUS IN (DONE) AND RESOLVED >= "2024/09/16" AND RESOLVED <= "2024/11/29""

(The "filter = 238820" is a nested filter that lists all of this squads members as the ticket assignee, it is how I add and remove people from squads easily, rather than have to change multiple filters each time someone moves).

I get a result of 75 issues returned.

I then applied the same filter to a control chart on the correct board for the squad, but only used the first part of the JQL filter (filter = 238820 AND component != "EDS (Internal) - Cost Down Idea"), I then use the chart itself to narrow down the statuses (In Progress and Done) and time frame. But this time get 33 issues listed.

The aim of this was to show my squad how their tickets are spread throughout the quarter in an effort to get them not to close their ticket once they are completed rather than leaving them till the end of the quarter.

Is anyone able to help me understand why using mostly the same filter can bring back two such different results?

In my mind the control chart should be showing me the same number of tickets as the JQL filter.

Danut M _StonikByte_ · Answer

Hi @Russell Haynes,

This might be due to the fact that the Control Chart report does some extra filtering.

For example, it might also look at the Resolution field. So if some of the issues from your filter are in Resolved status but they don't have a Resolution set, they might not be displayed in the report.  So please check this. Also, look at the timeline; it might not cover the timeline from your filter.

Also, if you are open to the idea of using a plugin from Atlassian Marketplace, our Great Gadgets app offers a Control Chart gadget that uses a JQL / filter as data input and it does not filter by other fields, like Resolution. This one will most likely display the issues from your filter.

Danut

Bill Sheboy · Answer

Hi @Russell Haynes -- Welcome to the Atlassian Community

Without seeing all the issues involved and the settings for the Control Chart, I suspect some of them are being excluded by the chart settings.

I recommend identifying a specific issue found by the filter but not shown on the chart and then review what is different to prevent the display.  That may lead to altering the chart settings to get what you need.  Unfortunately, this may be difficult with that built-in report because of the way it shows single versus groups of issues in clusters.

Kind regards,
Bill