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?
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.
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. :-(
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. :(
These workarounds may work but they are unacceptable to workaround lost functionality. I don't know the full roll of a Community Leader but you should discuss this with Atlassian and get them to do the right fix for this, i.e. continue to give us the full count but not render the full data to get the performance but paginate it. This shows poor programming skills on the Atlassian teams or unwise Product Managers. :-(
I just discovered this limitation going from hosted to cloud. Its a pretty major loss in terms of truly understanding your data. Its like you are only aware of the part of an iceberg above the water! Sure, you can use gadgets and API but with hosted Jira you would always know those numbers which gave you many insights as to the actual scale of things. Performance with this feature was pretty good so I don't agree with the argument that this feature had to go.
I find many things I really like about Jira Cloud but this is one I cannot get on board with. I hope the two dimensional and other gadgets show totals. At least I will be able to view scale withing leaving Jira web interface.
When to use CSV importer When managing your processes in Jira, there are many occasions where you need to create a lot of tasks. Creating them one by one will cost you a lot of time and effort and i...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events