How to limit JQL search result

Gavad Khan (PS) February 3, 2016

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.  

  • Issues fetched by Agile board
  • Issues fetched by Filter Gadget on JIRA dashboard
  • Issues fetched by Filter Gadget on Confluence page
  • Issues fetched by rest calls
  • Issues fetched by custom plugins

Is anybody did analysis in this area and find any alternate solution to limit JQL search result instance wide? 

 

3 answers

8 votes
Georges Moubarak
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
February 24, 2016

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.

2 votes
Pablo Beltran
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
April 19, 2016

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.

 

0 votes
David Perez Martorell October 14, 2022

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

Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
October 14, 2022

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.

Suggest an answer

Log in or Sign up to answer