Summary

As part of Search Experience API (https://community.developer.atlassian.com/t/rfc-61-evolving-search-capabilities-addressing-scalability-with-a-new-enhanced-search-api/83027), Jira users might receive errors when trying to use Apps > Open in Microsoft Excel or Open in Google Sheets.
Errors may sometimes seem unclear, such as:

Or display the error:

Unbounded JQL queries are not allowed here

This is us because the new experience prevents unbounded queries.

We do not recommend running unbounded JQL queries. These queries are slow for users and costly for every system involved. As our customers grow in number and size over time, we see customers with millions of Jira issues and this trend will continue.

We strongly recommend you bound your JQL queries to give our users the best performance and reliability. Consider bounding your queries like:

updated > -1m

Background

Bounded queries require a search restriction. Here are some examples of bounded queries:

project = TEST order by key
reporter = currentUser()

On the other hand, unbounded JQLs do not have any restrictions. They can be an empty query or one that solely lists order by clauses, such as:

order by createdDate
order by key

Jira JQL Expensive Operations

Recommendation

To improve user experience, Jira should provide more details about unbound queries or use AI to automatically flag the expression and give the user suggestions for rewriting the JQL.

The error should contain more information about what went wrong and there should be a public KB on how to rewrite JQL to avoid unbound errors