Uploaded image for project: 'Confluence Data Center'
  1. Confluence Data Center
  2. CONFSERVER-81276

Provide an option for Confluence to display more than 1000 issues while using Jira Issue Macro

    • Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • None
    • Macros - Jira Macros
    • None
    • 2
    • We collect Confluence 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.

      Issue Summary

      Jira Issue macro 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).

      This is reproducible on Data Center: yes

      Steps to Reproduce

      1. Edit a Confluence page and insert Jira issue macro.
      2. Search for a Jira project which has more than 1000 issues in it and insert.
        • By default JIM allows only 1000 results through display options

      Expected Results :

      JIM to display more than 1000 issues which are returned by Jira. 

      Actual Results :

      Confluence does not allow to add a number which is more than 1000 

      Workaround

      This problem can be circumvented by raising API limits within Jira, and utilizing Jira gadgets rather than the native macro within Confluence. This allows Jira to render the gadgets directly, instead of providing the raw data for Confluence to interpret. Both steps must be taken, as the default issue limit for Jira's API is 1000 issues— and this value is separately hard-coded in the native Confluence issue macro.

      This workaround will raise limits globally for all users and services that have API or export access. Larger requests have the potential to impact the performance of the instance or cause an outage— so it's important to use a limit that balances usability with the level of risk tolerance that is right for your organization.

      To enable the workaround:

      1. In Jira, navigate to Jira Administration > System > General Configuration > Advanced Settings.
      2. Change the following keys to the issue limit that you've decided on. Make sure to click the Update button to the right of each key after you've edited it.
        • jira.search.views.default.max
        • jira.search.views.max.limit
        • jira.search.stable.max.results
      3. In the <JIRA HOME>/jira-config.properties file, add the following line (or modify the value if the property is already present). If this file doesn't already exist, create it.
        • jira.table.gadget.max.rows = <MAX_ISSUE_LIMIT_HERE>
      4. Restart Jira.
      5. In Confluence, navigate to General Configuration > External Gadgets > Gadget Feeds.
      6. Enter the base URL for Jira in the Gadget Feed URL field, and click Add.
      7. Restart Confluence.

      After the workaround is complete, a few new macros will show up in the editor. The Filter Results macro provides similar functionality to the native issue macro, and will now be able to display issues up to the limit we just configured.

            [CONFSERVER-81276] Provide an option for Confluence to display more than 1000 issues while using Jira Issue Macro

            C A added a comment -

            Or please describe how to change the hard-coded limitations, as you stated: 

            "as the default issue limit for Jira's API is 1000 issues— and this value is separately hard-coded in the native Confluence issue macro."

            C A added a comment - Or please describe how to change the hard-coded limitations, as you stated:  "as the default issue limit for Jira's API is 1000 issues— and this value is separately hard-coded in the native Confluence issue macro."

            C A added a comment -

            Is it possible to provide an external Pugin/Solution or a Custom-Macro in order to overcome this limitation also for the PDF export case? 

            C A added a comment - Is it possible to provide an external Pugin/Solution or a Custom-Macro in order to overcome this limitation also for the PDF export case? 

            C A added a comment -

            The workaround may help to overcome the limit and I could get a rendered result at the webbrowser.

            BUT:

            How can the result be exported to  PDF document? This is not working. Probably, since the output is a dynamic rendering. The result is just empty.

            I do not understand, why it is not possible to overcome the limitation by changing the hard-coded limit within the Jira-Plugin or the Connector?

             

            I personally am crying to solve this problem sind 4 years, and we have invested >10K EURO into Atlassian products, still the support is not solved this critical issue for our business!

            Instead just multiple different tickets are generated, all of the pointing to the same basic problem (1000 limit) AND all of them "gathering interest". 

            I will suggest to my customers to use different products now and we will exit Atlassian product portfolio, if this is not solved soon.

             

             

            C A added a comment - The workaround may help to overcome the limit and I could get a rendered result at the webbrowser. BUT: How can the result be exported to  PDF document? This is not working. Probably, since the output is a dynamic rendering. The result is just empty. I do not understand, why it is not possible to overcome the limitation by changing the hard-coded limit within the Jira-Plugin or the Connector?   I personally am crying to solve this problem sind 4 years, and we have invested >10K EURO into Atlassian products, still the support is not solved this critical issue for our business! Instead just multiple different tickets are generated, all of the pointing to the same basic problem (1000 limit) AND all of them "gathering interest".  I will suggest to my customers to use different products now and we will exit Atlassian product portfolio, if this is not solved soon.    

              Unassigned Unassigned
              e4b6edf29732 Gopi Annepaka (Inactive)
              Votes:
              11 Vote for this issue
              Watchers:
              10 Start watching this issue

                Created:
                Updated: