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

Regression - JIRA Issues Macro fetching unnecessary fields from JIRA

XMLWordPrintable

      Environment

      • Confluence 6.6.x
      • Jira 7.6.x

      Steps to Reproduce

      1. Create a Confluence page.
      2. Insert the Jira Issues macro.
      3. Insert a JQL filter and include only specific custom fields you require.
      4. Save the Confluence page.
      5. Reload the page.
      6. Review the Jira access log regarding the request called.

      Expected Behavior

      Only specific custom fields as defined in the Jira issues macro will be searched. field=allcustom parameter should be removed.

      Actual Behavior

      All custom fields are being searched through and it causes the search to be extremely slow especially with instances comprised of large amount of custom fields. field=allcustom is apparent in the request URL e.g.

      http://localhost:53922/jira763/sr/jira.issueviews:searchrequest-xml/temp/SearchRequest.xml?jqlQuery=&field=summary&field=type&field=created&field=updated&field=due&field=assignee&field=allcustom&field=reporter&tempMax=1000

      Workaround

      Exclude custom field as column to display under the Display options. Please find the differences in the search request URLs below using the same JQL query. Note the field=allcustom parameter is removed when custom field column is not configured in the display options.

      With Custom FIeld
      127.0.0.1 672x266x1 admin [28/Jun/2018:11:12:40 +0200] "GET /jira/sr/jira.issueviews:searchrequest-xml/temp/SearchRequest.xml?tempMax=20&returnMax=true&jqlQuery=project+%3D+Scrum++&field=summary&field=type&field=created&field=updated&field=due&field=assignee&field=reporter&field=priority&field=status&field=resolution&field=allcustom&field=wonderful+choice&field=link HTTP/1.1" 200 3106 1174 "-" "Apache-HttpClient/4.5.5 (Java/1.8.0_131)" "q23bh4"
      Without Custom Field
      127.0.0.1 674x272x1 admin [28/Jun/2018:11:14:05 +0200] "GET /jira/sr/jira.issueviews:searchrequest-xml/temp/SearchRequest.xml?tempMax=20&returnMax=true&jqlQuery=project+%3D+Scrum+++&field=summary&field=type&field=created&field=updated&field=due&field=assignee&field=reporter&field=priority&field=status&field=resolution&field=link HTTP/1.1" 200 1735 71 "-" "Apache-HttpClient/4.5.5 (Java/1.8.0_131)" "lw2vqt"

            [CONFSERVER-56017] Regression - JIRA Issues Macro fetching unnecessary fields from JIRA

            Philippe PEREZ added a comment -

            Thanks @James !

            Philippe PEREZ added a comment - Thanks @James !

            James Ponting added a comment -

            Hey All,

            Quick update on this one.

            We've re-opened the investigation on this one at CONFSERVER-80386: JIRA Issues Macro fetching unnecessary fields from JIRA as the f63499f72ff5 team mentioned (thank you for that too ).

            We'll update that ticket as our investigation proceeds.

            Thanks,
            James Ponting
            Engineering Manager - Confluence Data Center

            James Ponting added a comment - Hey All, Quick update on this one. We've re-opened the investigation on this one at CONFSERVER-80386: JIRA Issues Macro fetching unnecessary fields from JIRA as the f63499f72ff5 team mentioned (thank you for that too ). We'll update that ticket as our investigation proceeds. Thanks, James Ponting Engineering Manager - Confluence Data Center

            AMP Admin Email Account added a comment - - edited

            This bug is confirmed by Atlassian support that it re-occurs in Confluence versions post 7.13.8. Please upvote below:

            https://jira.atlassian.com/browse/CONFSERVER-80386

            AMP Admin Email Account added a comment - - edited This bug is confirmed by Atlassian support that it re-occurs in Confluence versions post 7.13.8. Please upvote below: https://jira.atlassian.com/browse/CONFSERVER-80386

            AMP Admin Email Account added a comment - - edited

            We're still seeing this Confluence v7.19.2 as well.

            Looks like this issue exists in all versions post Confluence v7.13.8

            Updated Jira Issue Macro plugin (v 11.5.10), but it doesn't resolve.

            Is there any way to escalate this? Coz, it's having a serious impact on performance.

            AMP Admin Email Account added a comment - - edited We're still seeing this Confluence v7.19.2 as well. Looks like this issue exists in all versions post Confluence v7.13.8 Updated Jira Issue Macro plugin (v 11.5.10), but it doesn't resolve. Is there any way to escalate this? Coz, it's having a serious impact on performance.

            Andrew Pane added a comment -

            We're still seeing this in 8.13.22.

            Andrew Pane added a comment - We're still seeing this in 8.13.22.

            Martin Jerome Raj added a comment -

            The bug still in 7.13.5...

            Martin Jerome Raj added a comment - The bug still in 7.13.5...

            Zac Xu added a comment -

            Hi thomas.weissschuh893360640,

            I just checked this fix has been shipped since 7.4.7. I updated the fix version for this ticket accordingly. 

            Cheers,

            Zac Xu added a comment - Hi thomas.weissschuh893360640 , I just checked this fix has been shipped since 7.4.7. I updated the fix version for this ticket accordingly.  Cheers,

            Thomas Weißschuh added a comment -

            @Niraj Any updates about the backport to 7.4 LTS?

            Thomas Weißschuh added a comment - @Niraj Any updates about the backport to 7.4 LTS?

            Jason Unsworth added a comment -

            Niraj, thanks for confirming.

            Jason Unsworth added a comment - Niraj, thanks for confirming.

            Niraj Bhawnani added a comment -

            Hi Jason,

            Thanks for letting us know about that. I've cleared the Fixed in LTS field to reflect the updated status of this issue. As this change was quite complex and touched on a number of areas in the Jira Issues Macro plugin, we feel like the change introduces more risk than we'd normally be comfortable with shipping straight to an LTS release. In about a month we will reevaluate what the status of this is based on whether any new issues were found that relate to the fix. If we don't find further issues, we will likely choose to start work to backport the changes to the 7.4 LTS release. Thanks for understanding.

            Regards,
            Niraj Bhawnani
            Engineering Manager - Confluence Server
            Atlassian

            Niraj Bhawnani added a comment - Hi Jason, Thanks for letting us know about that. I've cleared the Fixed in LTS field to reflect the updated status of this issue. As this change was quite complex and touched on a number of areas in the Jira Issues Macro plugin, we feel like the change introduces more risk than we'd normally be comfortable with shipping straight to an LTS release. In about a month we will reevaluate what the status of this is based on whether any new issues were found that relate to the fix. If we don't find further issues, we will likely choose to start work to backport the changes to the 7.4 LTS release. Thanks for understanding. Regards, Niraj Bhawnani Engineering Manager - Confluence Server Atlassian

              zxu2@atlassian.com Zac Xu
              syong@atlassian.com Sean Yong
              Affected customers:
              34 This affects my team
              Watchers:
              51 Start watching this issue

                Created:
                Updated:
                Resolved: