JQL no longer displaying total number of issues if over 1000 issues returned?

[Lorraine Gorman]

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?  

[Edie Hovermale · Accepted solution]

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. 

[Edie Hovermale]

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. :-(

[Lorraine Gorman]

Thanks @Edie Hovermale.  I agree. Alternatively, we are setting up confluence page tables with fiscal year counts that tend to be larger than 1000+

[Lorraine Gorman]

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.

[Edie Hovermale]

@Lorraine Gorman , That is interesting. We have Service Desk that must be why I see it. Alternatively you could do a pie chart or heat map on status'. They both show the Total number.

See attached:

[Yevgen Lasman]

It looks like Atlassian makes it difficult even for workarounds to be applied 🤦🏼‍♂️

[John Funk · Accepted solution]

Hi Lorraine - I am experiencing the same thing. Trying to get some feedback, but none received yet. 

[Edie Hovermale]

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?

[Lorraine Gorman]

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:

• JIRA Cloud REST API - Reference

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

[John Funk]

@Lorraine Gorman  - Thanks for the update. 

[John Funk]

I am using the Jira Cloud for Excel (Early Access) free plug-in. I was able to relatively quickly open a filter in Excel and download all of the issues (or just put in a JQL query on the spot. Not ideal, but it worked. 

[Lorraine Gorman]

Thanks @John Funk I will give that add-on a try.  

[John Funk]

If that works for you, can you click on the Accept answer button above so we can close this out? If it doesn't let me know if there is something I can help with.  :-)

[Edie Hovermale]

John,

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. :-(

[John Funk]

Hi Edie - I am just a user like you. I can pass along your comments, by you should do that directly with Atlassian. 

[Edie Hovermale]

Thanks John - I just put in a support request but knowing Atlassian they will most likely do nothing. :-(

[Dana Frost]

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.

[Jeff Doyle]

I have to perform analysis going back to 2019 for R&D tax credits.  Having this as a limitation is making my job a lot harder.  If I can run the query to get 1000 then I should be able to run another query to get the 2nd/3rd/4th 1000.  I get that they're trying to protect their Dbs and don't want to returns giant datasets but at least allow the user to get the results in chunks of 1000

[Amir Katz (Outseer)]

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):

• Run your search
• Export --> Print list
• A new browser tab will open
• In the top left, you will see the count:

• Close this tab
• Retrieve your Atlassian Voodoo doll, prick it again

BTW, exporting to CSV only exports 1000 tickets, so it's not a solution...

[Tim Mackinnon]

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...

[Amir Katz (Outseer)]

Would appreciate if you mark my answer as Accepted. Hate to do it myself...

[Ramon Padilla]

This is the best answer.

[Lance Carnow1]

Agree with @Ramon Padilla !  This is THE best answer - appreciate your response, @Amir Katz (Outseer)  !!

[Ger Bakker]

Hi @Amir Katz (Outseer) You made my day. What a wonderful and easy solution to the problem! Thank you so much. Simply supercalifragilisticexpialadocious!! Thanks once again.

[Amir Katz (Outseer)]

Thank you! Wonderful? OK... easy? not so much...Solution? it's an ugly a hack :-)

[Jean-Christophe GONZALES]

Thank you so much for this trick

[Graf Bishop]

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!).

[Gary Peek]

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.

[Dale Fernandes]

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.