Any limits on rows to search/show tickets with "Advanced Search" function?

Yusuke Nakayama September 20, 2018

Hello Jira Software users and experts,

I wonder if there are any limits on search tickets with JQL (in Advanced Search function).

 

I am currently using Jira Software in my company and try to do an 'Advanced Search' to all tickets in every project we have now in order to monitor how many tickets are entirely created and its status.

  

The JQL I run was like below, and it showed "An unknown error occurred while trying to perform a search" and doesn't show the tickets that satisfy the conditions in JQL.

project in (BRA, BRARA, BRARARA) and createdDate >= '2017-01-01' and cf[11111] != sample

 

I have tried three things to see what would be the root causes,

1: search single project => in some projects don't work (for the projects having numerous tickets more than 100,000 )
2: search with recent date (like createdDate >= '2018-01-01') => works
3: search without custom field => doesn't work

Any work arounds would be also very appreciated.


Thank you.

1 answer

0 votes
Daniel Deng
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.
September 20, 2018

Hi

In JIRA, there is a default limit of 1000 rows set on the number of issues that can be returned in the Issue Navigator.  This is done to prevent unnecessary performance degradation.

Please have a look at: https://confluence.atlassian.com/jirakb/how-to-increase-the-jira-search-results-limit-on-the-issue-navigator-357696242.html?_ga=2.221118097.805528079.1537141494-1862115692.1524199642

As for your case, hard to tell the root cause. I would recommend you simplify your search to identify the problem, for example

1. Try this project in (BRA), project in (BRARA), project in (BRARARA) separately

2. Try to remove the custom field search: project in (BRA, BRARA, BRARARA) and createdDate >= '2017-01-01'

3. Extend or move back the timing to "2018-01-01" or 2016-01-01

Anyway, start from a simple workable jql and extend it progressively to identify the root cause

Yusuke Nakayama September 20, 2018

Hello Daniel,

Thank you for your reply.


>hard to tell the root cause. I would recommend you simplify your search to identify the problem

That's true.
And I missed to wrote what I have tried to figure out root causes.

I tried 3 things, 

1: search single project => in some projects don't work (for the projects having numerous tickets more than 100,000 )
2: search with recent date (like createdDate >= '2018-01-01') => works
3: search without custom field => doesn't work

thus I assume that there might be some limits on 'Advanced Search' especially when we try to pull so many data.

That's why I post this question regarding the limits on 'Advanced Search'.

Yusuke Nakayama September 20, 2018

(note: added what I have done to figure out the root causes)

Daniel Deng
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.
September 20, 2018

Hi Yusuke

Thanks for the clarification. I believe Jira does not have a limitation of number of issues in a project. Your case looks like a bug or configuration problem, probably you need to contact Atlassian tech support directly.  

Yusuke Nakayama September 20, 2018

Hello Daniel,

 

Thank you for your advice.

I am going to ask Atlassian tech support directly.

 

Thank you for your time :)

Suggest an answer

Log in or Sign up to answer