-
Bug
-
Resolution: Fixed
-
High
-
6.4.3, 6.6.6, 6.13.10, 7.0.4, 7.4.0, 7.4.3, 7.5.2, 7.6.0, 7.6.2, 7.4.2
-
34
-
Severity 2 - Major
-
132
-
Environment
- Confluence 6.6.x
- Jira 7.6.x
Steps to Reproduce
- Create a Confluence page.
- Insert the Jira Issues macro.
- Insert a JQL filter and include only specific custom fields you require.
- Save the Confluence page.
- Reload the page.
- 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"
- causes
-
JRASERVER-67095 JIRA XML API takes a long time to return XML data (search request)
- Closed
- has a regression in
-
CONFSERVER-80386 JIRA Issues Macro fetching unnecessary fields from JIRA
- Closed
- is a regression of
-
CONFSERVER-29292 JIRA Issues Macro fetching unnecessary fields from JIRA
- Closed
- is related to
-
CONFSERVER-60050 Custom Fields are missing in Jira Issue Macro after upgrade to Confluence 7.4.1, 7.5.0, 7.6.0
- Closed
-
CONFSERVER-60029 Jira Macro doesn't display`Epic Name`, `Epic Colour` and `Epic Status` values
- Closed
-
CSP-276497 Loading...
-
PSR-409 Loading...
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...