Returned issue limit in query

[Jason Dyke]

When embedding a a JIRA query in a confluence page, the text indicates 'showing 1000 out of 1745 issue'. My desire is to use this in a table excerpt that can later be filtered down for more specific results but im finding that the additional 745 issues will never show up. Is there a way to display these or turn off the limit of how may values are returned? And if there is a way to return all results in a query regardless of number, is there any downsides or other issues I would run into?

[Danno]

@Jason Dyke unfortunately you are running up against a limit with the tool. The maximum number of results you can get is 1000.

[Jason Dyke]

know of any clever ways to use a 2nd query to return a 2nd set of 1000? ie use 2 queries, one displaying issues 1-1000 and a 2nd showing 1001-2000?

[Danno]

Two separate filters based on dates perhaps? I'm not sure why you would want to display that many issues on one page. It will be a short amount of time before you hit 2000 issues.

Without knowing how you are working in your Jira instance, I would at least break up your searches by project perhaps or maybe components or Epics to reduce the number of issues returned. Also leave out closed issues by resolution or status category. With that one you might still want to see recently closed issue so you would need to filter by a function such as startOfYear() or startOfMonth().

[Richard Cho - ServiceRocket]

@Jason Dyke Have you tried embedding the query as a Confluence database? I tried it out and I was able to query and display over 2000 issues just fine. The initial step of connecting to the data can take several minutes though and it makes my browser lag pretty hard (not sure why this step is so unoptimized). Once it finishes though it becomes responsive again.

You can get started by reading this: https://support.atlassian.com/confluence-cloud/docs/create-a-database/

[Danno]

@Richard Cho - ServiceRocket that is interesting. I haven't worked with the database tool yet and I am surprised to find out it is capable of returning more issues than a JQL search. Do you have any insights as to why other than the somewhat typical disjointed Atlassian way of doing things?

[Jason Dyke]

@Richard Cho - ServiceRocket  thanks for the suggestion. will look into that as an option. At first look I am not seeing a way to use filters or options in table toolbox to manipulate the data further within a confluence page that calls that database.

[Jason Dyke]

I think i found the answer to that
Solved: Integration of Confluence Databases

[Richard Cho - ServiceRocket]

@Danno No insights from my side I'm afraid, although I just found out that there's a newer version of the Jira issues macro which works similarly to my database example but it seems like it only displays a portion of the total results and forces you to scroll down to load the next batch of results. Doesn't seem very ergonomic in my opinion -- would rather have the data upfront.