ssue Nav requests /rest/api/2/filters/favourite?expand=subscriptions[-5], which means that it'll return a list of all of the user's favourite filters, where every filter will also include a list of everybody who subscribes to that filter.

Why does it need the list of subscribers if it only shows a list of filters?

It seems I accidentally committed all my changes for this issue using a key of JDEV-36172 instead of JRA-36172

Was merged, new KA released (I think), but seems I forgot to change the issue status. Should be in JIRA master now.

In the process of building and releasing a new version of KickAss, but there's test failures caused by recent changes to JIRA master

I reject it:

• New version of issue nav plugin was not released
• Kickass version was not bumped

kujbusn, as Chris mentioned above, this issue will occur in edge cases - instances with hundreds of filters and multiple subscriptions. Whether your instance would be affected after an upgrade depends on the size of it. If you wish to discuss a specific case further, feel free to open a case at support.atlassian.com.

What is the workaround until it's get fixed? How can we determine how many filters or subscriptions are sufficient? It's working fine in 5.1.x but not in 6.1, so it's a blocker in our Jira upgrade project.

Issue Nav requests /rest/api/2/filters/favourite?expand=subscriptions[-5], which means that it'll return a list of all of the user's favourite filters, where every filter will also include a list of everybody who subscribes to that filter.

If a user had hundreds of filters, and there were several dozen subscriptions to each, the response size would be huge. If it was sufficiently huge, that could cause timeouts for the request, meaning the browser gets an empty response. That empty response is then getting misinterpreted by the Issue Nav, and causes some knock-on effects of the issue nav not working.