Saved filter query throwing an error

Question

I have a saved filter query which I add fix versions across multiple teams to be able to export the data for a deployment report.

The query works up to a certain point then I get an oops page and when I minimize the size, of which the data is not that much) I am used to 1000+ data and no issues. In this case the current data is about 437 rows.

When I downsize the saved filter seems to have gone into a "broken" state as I then continue to get the oops error and not being able to download anymore.

The last successfull export was at 388 rows

When I copy the filter that seems broken and download then it is fine, but when I add more fix version for data then the copied filter breaks again

I really don't want to copy and copy each time

Would a potential factos be if the fix version is released vs not released?

Utkarsh Agarwal · Answer

Hi @Lelani Mayer

This sounds like a performance limitation rather than an actual issue with the filter itself. While 437 issues isn’t typically a problem, the number of fixVersion values being queried — especially across multiple projects — can increase the complexity of the JQL and the load on the UI/export functions.

I’ve seen similar behavior where the filter works fine up to a point and then starts throwing “Oops” errors once the query grows, particularly when exporting to CSV. Copying the filter essentially resets it temporarily, but once it hits that threshold again, it breaks — so the problem persists.

The released status of a fixVersion shouldn’t impact the query execution unless your JQL specifically filters by it. That said, released versions could potentially bring in more linked metadata, which might add to the render/export load.

A couple of things you could try:

* Use the REST API for exporting results — it handles large datasets more gracefully than the UI.
* If possible, simplify the query by limiting the number of fixVersions or breaking them into smaller, modular filters.
* If this keeps happening at a predictable point, it’s worth opening a support ticket so Atlassian can check what’s happening behind the scenes.

Kind Regards
Utkarsh

Aditya Verma · Answer

Hi @Lelani Mayer ,

Whether Fix Version is released or unreleased should not have direct impact on filter stability or query execution.
Can you please provide the query here and also screenshot of the error you are receiving.

Thanks,

Aditya