Custom Field Values Show Differently Due to Name Clashing in JIRA Issue Macro
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
Symptoms
When a user inserts a JIRA Issues macro into a Confluence page, they are unable to see the appropriate value. Instead, the value returned is the one from a built-in field.
The macro appears similar to the following:
Where it should be displayed as:
Diagnosis
When checking the XML view of the JIRA issue, the built-in fields clash with the custom fields name.
Cause
The custom field name has the same name as the default field.
Solution
Workaround
The custom field needs to be renamed so that the JIRA issues macro shows its value. For more information regarding the reserved name for built-in fields, please refer to What is an Issue.
Was this helpful?