Details
-
Bug
-
Resolution: Unresolved
-
Medium
-
None
-
7.13.11, 7.13.12, 7.19.1, 7.19.4, 7.13.14, 7.19.9
-
25
-
Severity 2 - Major
-
9
-
Description
Issue Summary
Since upgrading to Confluence 7.3.1 to 7.19.1 customer is reporting that values of custom fields are not returning and not being displayed
Bug Behaviour
The behaviour of the bug is in such a way that if a user’s Jira Issue Macro has a custom fields to be returned from Jira, these fields are not retuned.
Steps to Reproduce
- Install Confluence 7.3.1
- Install Jira 8.20.12
- Create a few issues on Jira with one custom field name Custom First and populate it
- Create an applink between Confluence to Jira
- Create a page named JIM731 in Confluence with a Jira Issue Macro with these property
- Filter: project = <Key of the project where the issue have been created>
- Field: Add Custom First to the field to display
- Upgrade Confluence to 7.19.1
Expected Results
Requested custom fields are returned from Jira to Confluence and displayed.
Actual Results
Requested custom fields are empty in Confluence.
Additional notes
Storage format of the Macro which fails after upgrade to Confluence to 7.19.1:
<p><ac:structured-macro ac:name="jira" ac:schema-version="1" ac:macro-id="aaa503f3-6574-4862-87d3-f6479f8fe76d"><ac:parameter ac:name="server">InstEnv Jira</ac:parameter><ac:parameter ac:name="columns">key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution,custom first</ac:parameter><ac:parameter ac:name="maximumIssues">20</ac:parameter><ac:parameter ac:name="jqlQuery">project = MP </ac:parameter><ac:parameter ac:name="serverId">1131c139-68c6-3e50-86c7-8832ad59e376</ac:parameter></ac:structured-macro></p>
Storage format of the macro created after upgrading:
<p><ac:structured-macro ac:name="jira" ac:schema-version="1" ac:macro-id="dd735e93-3d1f-4cfd-aa24-0ffd5d0f1c23"><ac:parameter ac:name="server">InstEnv Jira</ac:parameter><ac:parameter ac:name="columnIds">issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution,customfield_10105</ac:parameter><ac:parameter ac:name="columns">key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution,Custom First</ac:parameter><ac:parameter ac:name="maximumIssues">20</ac:parameter><ac:parameter ac:name="jqlQuery">project =MP </ac:parameter><ac:parameter ac:name="serverId">1131c139-68c6-3e50-86c7-8832ad59e376</ac:parameter></ac:structured-macro></p>
The newly created macro has this additional section in it:
<ac:parameter ac:name="columnIds">issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution,customfield_10105</ac:parameter>
Workaround
Delete and recreate the affected macro.
Attachments
Issue Links
- is cloned from
-
-
- Closed
-
- is duplicated by
-
-
- Gathering Impact
-