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

Ability to configure the maximum number of issues displayed in the JIRA issues macro

    • 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.

      NOTE: This suggestion is for Confluence Server. Using Confluence Cloud? See the corresponding suggestion.

      In earlier versions, the JIRA issue macro had a pagination feature. This feature was removed due to observed low feature usage, in addition with our strategic focus to simplify the Confluence user interface and to keep and complex JIRA operations in JIRA. My apologies for the may customers that were quickly impacted by this, we could have done a better job in communicating this and ensuring we had understood your needs with regards to this matter.

      Since then we've received a lot of feedback to bring back pagination. Thank you for those of you who provided helpful comments below, and for those customers we have been able to speak to about this. With this in mind, we have concluded the following:

      • It is very clear that the current issue limit we have is insufficient and does not meet most of your needs.
      • It is important for you to be able to see all the issues requested
      • We still believe that the use case of navigating 100+ issues within inside Confluence is something that is extremely low and is something which should be done in JIRA.
      • Some of you mentioned of the importance of seeing this also in PDF exports when you share the release notes or pages with customers.

      With that in mind, what will we be doing to address this?
      1. We will look at increasing the limit of the total number of visible issues
      2. In addition, we will look at providing a parameter to configure this.
      Note: You will always be limited by the total amount of issues JIRA provides, but this setting can be changed.
      3. We will be looking at also implementing CONF-30114 (sorting) to assist with dealing with larger issue lists in Confluence.

      Thank you all for your patience in this matter, we will update this issue as we make progress.

      Sherif Mansour
      Confluence Product Manager

      Previous description:

      The new JIRA issues macro does not paginate. This feature request is to help us better understand why customers want this.
      If you are going to comment on this ticket, please provide some understanding for why you want pagination. We removed this feature because we saw very low usage of it. Since then, we've had a few requests to bring it back.

      One way we could solve the majority use case is to increase the default amount of search results displayed. We are a bit hesitant to bring this back as we want to understand what it is that we are missing. If you are embedding 50/100+ issues on a page and want pagination, you probably shouldn't be doing that in Confluence, but rather the JIRA issue navigator - that is why we tell you "there are xxx more issues, open in JIRA".

      Please help us understand why you want this and some examples where you really do have lots of issues on a page that you want your end-users to read (if that is the use case)

            [CONFSERVER-30116] Ability to configure the maximum number of issues displayed in the JIRA issues macro

            Hailin Zhang added a comment - - edited

            Thanks Nguyen, I have fixed the issue by using url & tempmax parameter of the jira macro like
            <ac:structured-macro ac:name="jira">
            <ac:parameter ac:name="columns">Created,Due,Key,Summary,Priority,Reporter,Assignee,Dcc Impacting,Resolution,Risk - Overall</ac:parameter>
            <ac:parameter ac:name="server">JIRA Server</ac:parameter>
            <ac:parameter ac:name="title">Resolved Requests</ac:parameter>
            <ac:parameter ac:name="width">98%</ac:parameter>
            <ac:parameter ac:name="height">450</ac:parameter>
            <ac:parameter ac:name="cache">off</ac:parameter>
            <ac:parameter ac:name="renderMode">dynamic</ac:parameter>
            <ac:parameter ac:name="url">
            <ri:url ri:value="https://testjira.com.au/sr/jira.issueviews:searchrequest-xml/temp/SearchRequest.xml?jqlQuery=project+%3D+TEST+AND+status+IN+(Resolved);tempMax=300"/>
            </ac:parameter>
            </ac:structured-macro>

            Hailin Zhang added a comment - - edited Thanks Nguyen, I have fixed the issue by using url & tempmax parameter of the jira macro like <ac:structured-macro ac:name="jira"> <ac:parameter ac:name="columns">Created,Due,Key,Summary,Priority,Reporter,Assignee,Dcc Impacting,Resolution,Risk - Overall</ac:parameter> <ac:parameter ac:name="server">JIRA Server</ac:parameter> <ac:parameter ac:name="title">Resolved Requests</ac:parameter> <ac:parameter ac:name="width">98%</ac:parameter> <ac:parameter ac:name="height">450</ac:parameter> <ac:parameter ac:name="cache">off</ac:parameter> <ac:parameter ac:name="renderMode">dynamic</ac:parameter> <ac:parameter ac:name="url"> <ri:url ri:value="https://testjira.com.au/sr/jira.issueviews:searchrequest-xml/temp/SearchRequest.xml?jqlQuery=project+%3D+TEST+AND+status+IN+(Resolved);tempMax=300"/> </ac:parameter> </ac:structured-macro>

            hailin.zhang Sorrry for the confusing, 5.3.4 is the version of Confluence which bundles the fix version of JIRA Issues Macro. This is the list of Jira Macros version, 5.2.2 is probably the version you need.

            Nguyen Dang added a comment - hailin.zhang Sorrry for the confusing, 5.3.4 is the version of Confluence which bundles the fix version of JIRA Issues Macro. This is the list of Jira Macros version , 5.2.2 is probably the version you need.

            Hailin Zhang added a comment - - edited

            Hi there, where can I download jira macro 5.3.4? I cannot see it on the marketplace list.
            We are using confluence 5.3.4. So there is no way to resolve the 20 limitation issue?

            Hailin Zhang added a comment - - edited Hi there, where can I download jira macro 5.3.4? I cannot see it on the marketplace list. We are using confluence 5.3.4. So there is no way to resolve the 20 limitation issue?

            dv20tst You can try the 5.1.3 version of the plugin which has the feature and is Confluence 5.2.5 compatible.

            Nguyen Dang added a comment - dv20tst You can try the 5.1.3 version of the plugin which has the feature and is Confluence 5.2.5 compatible.

            Hello,
            I dont find the button "Maximum issues"
            I Use Confluence 5.2.5
            can you help me please?
            Cheers Thomas

            Thomas Strempel added a comment - Hello, I dont find the button "Maximum issues" I Use Confluence 5.2.5 can you help me please? Cheers Thomas

            We see this at the bottom of our JIRA issue macro list
            Showing 20 out of 38 issues

            Where "38 issues" is a link to JIRA . . . which is fine, except for when we are displaying custom fieldscolumns in the JIRA list.
            We lose our custom fields when we are taken to JIRA. That is annoying.

            Sam Livingston added a comment - We see this at the bottom of our JIRA issue macro list Showing 20 out of 38 issues Where "38 issues" is a link to JIRA . . . which is fine, except for when we are displaying custom fieldscolumns in the JIRA list. We lose our custom fields when we are taken to JIRA. That is annoying.

            Anatoli added a comment -

            robin@date.net, 1000 is the typical limit that JIRA itself imposes.

            Anatoli added a comment - robin@date.net , 1000 is the typical limit that JIRA itself imposes.

            Robin Toop added a comment -

            Actually if you leave it empty if fills it with 1000 when you hit enter. Its not like before but at least a large number.
            So how do I add this parameter to the wiki import string?, If I use the default, it still reverts to 20

            Robin Toop added a comment - Actually if you leave it empty if fills it with 1000 when you hit enter. Its not like before but at least a large number. So how do I add this parameter to the wiki import string?, If I use the default, it still reverts to 20

            Anatoli added a comment -

            Hi tnorton,

            it is possible by leaving the limit field empty:

            Anatoli added a comment - Hi tnorton , it is possible by leaving the limit field empty:

            I also want the ability to view all issues in a filter in Confluence, without limiting to 20 results and directing to Jira. In my case it's a list I provide to the business to see all the things in our bucket. Plus I browse them on the same page. It's a bird's eye view and helps me stay aware. I rely on this. Is this "the feature" you are talking about is available in version 5.1.3?

            Tim Norton added a comment - I also want the ability to view all issues in a filter in Confluence, without limiting to 20 results and directing to Jira. In my case it's a list I provide to the business to see all the things in our bucket. Plus I browse them on the same page. It's a bird's eye view and helps me stay aware. I rely on this. Is this "the feature" you are talking about is available in version 5.1.3?

              tvu TruongA
              smansour Sherif Mansour
              Votes:
              43 Vote for this issue
              Watchers:
              50 Start watching this issue

                Created:
                Updated:
                Resolved: