Hi all -- we are using Cloud version. We used to get the total number of issues returned when running a JQL query --- even when the count was greater than 1000 it would be the exact number of issues that satisfied the query. I know export only works for up to 1000 issues but now the value returned and that is displayed is "1000+". I'm not sure when this changed. Is there another way now to get the total count of issues on a returned query?
Hi Lorraine - I am experiencing the same thing. Trying to get some feedback, but none received yet.
Lorraine,
Thanks for getting back to us on the answer from Atlassian. Poor workaround from them.
:-(
My solution to work around the issue was to save the query filter that contains the full number I need then create a dashboard and add the 'Filter counts' widget and use the saved query filter. See attached.
This is not great. My teams are experiencing the same thing. It some cases we really need to know the full number. Why does Atlassian continue to take functionality away. What is wrong with them?
So I heard back from the Atlassian support. Seems this was an intentional change (or a result of an intentional change) as part of system-wide optimizations to improve the scale and performance of our Cloud infrastructure. Included is a new limitation on the max number of issues listed on a single page of a query, which will render any search totals that go above 1000 entries as "1000+".
As of this moment, there isn't any way to bypass this particular functionality. If you need an exact number of issues pertaining to a JQL query, you should still be able to do so externally through the REST API.
Then they sent me this KB article detailing the functions available within the REST API:
Honestly I think they are out of touch a bit with the needs of the user community. They took one thing away to address another. Using the API is not a solution for something that we had with one quick query before.
Anyway, for now we are creating tables in Confluence and using the JIRA macro getting and displaying counts there.
Lorraine
@Lorraine Gorman - Thanks for the update.
I just can't believe I have to tell all of my users that have to do a workaround to something that used to work easily and cleanly. Doesn't Atlassian realize they can get a count without rendering the data? Just getting a count should not have performance issues. :-(
Thanks @Edie Hovermale. I agree. Alternatively, we are setting up confluence page tables with fiscal year counts that tend to be larger than 1000+
BTW @Edie Hovermale the "Filter Counts" gadget is not available for me. I looked to see why and it seems it is only available if you have Jira Service Desk. We do not have JSD.
I agree this is an unacceptable loss along with the loss of the pagination entirely. @atlassian Team, please consider putting this back (I am using Jira Server 8.13.1).
However, there is an easy & quick (partial!) workaround... simply click on the Tools menu in the top-right and this gives you a count (but only if the query returns less than 1000 records!).
Our organisation is in the process of migrating from Data Centre to Cloud but little things like this really make we wish we weren't. Especially as when wanting to do some really simple things like validate some data betwen the two instances - like how many issues exist between the two..Data Centre just tells you the total, but Atlassian make this painfully impossible...awful.
If you select a Project, and then select Releases from the left menu, then click on a release version, it will show you the total number of stories in the system for that release.
I totally agree this is a major degradation. The Jira Cloud product managers are totally disconnected from their users (and I'm being polite here).
Anyway, here is an ad-hoc workaround (which requires neither any add-ons, nor creating any dashboards):
BTW, exporting to CSV only exports 1000 tickets, so it's not a solution...
OMG - this answer is so useful thank you! Yet again Atlassian makes another dumb product decision... and it will take 10 years to fix it (if ever). Voodoo doll has little space left for any more pins...
Would appreciate if you mark my answer as Accepted. Hate to do it myself...
This is the best answer.
It looks like you're new here. Sign in or register to get started.
