I just done through with above Atlassian documentation and found that there is no way to control/limit JQL max issues result for following scenarios. This has also confirmed by Atlassian premium support consultant.
Is anybody did analysis in this area and find any alternate solution to limit JQL search result instance wide?
Hi @Gavad Khan,
I suggest to refine your search to include, for example, issues updated in the last 10 days. In this way you can limit the search result.
A similar issue has been resolved by some users by using SQL for JIRA as it supports the LIMIT command (among others like MAX and MIN based on issue field values).
You can transform your JQL into a SQL, limit the results by setting a LIMIT or whatever other SQL-based alternative and then get the issues as JQL again by transforming the SQL into a new JQL with the built-in sql function.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
hello, it could be very good to extend number of rows in export reports or to add limit in jql query.
let's see alternative solutions
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Um, no.
Increasing the export limits renders your server unperformant (plus, humans struggle with large data sets, large exports tend to be useless to them)
Limiting results is only useful in a technical context. Your users don't want to be working with truncated data sets.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.