Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-71188

Eliminate the 1000 row return limit in the Jira Issues Macro

XMLWordPrintable

    • 2
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      I've learned the Jira Issue macros will only return a max of 1000 rows regardless of emptying the Maximum Issues field (where it says it will return all rows if empty).  We develop Confluence dashboards that aggregate data returned in Jira Issue macros using the Pivot Table macro.  Not allowing all rows to return from queries that return more than 1000 rows results leaves Pivot Table results inaccurate.  I would like to ask for this limitation to be removed or configurable.

            [JRASERVER-71188] Eliminate the 1000 row return limit in the Jira Issues Macro

            Lucas Downard added a comment -

            We are interested in this as well.  The workaround utilizing the Filter Results macro does not provide the same functionality for us

            Lucas Downard added a comment - We are interested in this as well.  The workaround utilizing the Filter Results macro does not provide the same functionality for us

            C. B*** added a comment -

            +1

            Same problem here.

            While the Jira Instance allows for 1000+ results to be received by query, the Confluence macro sets a hard limit of 1000 issues per table. The total number of issues, is e.g. displayed with 1500 and the implied "leave free, to receive all issues" auto fills with 1000 if left free. Typical Confluence / Atlassian experience.

            C. B*** added a comment - +1 Same problem here. While the Jira Instance allows for 1000+ results to be received by query, the Confluence macro sets a hard limit of 1000 issues per table. The total number of issues, is e.g. displayed with 1500 and the implied "leave free, to receive all issues" auto fills with 1000 if left free. Typical Confluence / Atlassian experience.

            Martin Wilkinson added a comment -

            We encountered the same issue.  The Macro itself will return the correct totals but if you want a list it stops at 1000 rows.  This is a serious limitation that is impacting a global development workforce that relies on both confluence and Jira to work together.  Frankly put if this is a limitation and an enhancement request i am stunned as the "leave empty to get all issues" field indicates this should work - its a bug that should be fixed

            Martin Wilkinson added a comment - We encountered the same issue.  The Macro itself will return the correct totals but if you want a list it stops at 1000 rows.  This is a serious limitation that is impacting a global development workforce that relies on both confluence and Jira to work together.  Frankly put if this is a limitation and an enhancement request i am stunned as the "leave empty to get all issues" field indicates this should work - its a bug that should be fixed

            mwilder added a comment -

            The confluence macro appears to have it's own 1000 issue limit while you can configure the limit in Jira to be something higher. It seems the limit of the macro should mirror the limit set in Jira but it doesn't appear to be. This issue is a bit old but I'm looking to solve this same problem.

            mwilder added a comment - The confluence macro appears to have it's own 1000 issue limit while you can configure the limit in Jira to be something higher. It seems the limit of the macro should mirror the limit set in Jira but it doesn't appear to be. This issue is a bit old but I'm looking to solve this same problem.

            Jordan Janis added a comment -

            +1

            A 1000 issue limit is bad enough - but the UI should not imply that you can raise the limit, or "leave empty to get all issues."  Is there some configuration parameter that can increase this limit as there is for search results?

            Jordan Janis added a comment - +1 A 1000 issue limit is bad enough - but the UI should not imply that you can raise the limit, or "leave empty to get all issues."  Is there some configuration parameter that can increase this limit as there is for search results?

              Unassigned Unassigned
              de86cedb8ae5 BMJ Ventures
              Votes:
              36 Vote for this issue
              Watchers:
              32 Start watching this issue

                Created:
                Updated: