Custom Field Values Show Differently Due to Name Clashing in JIRA Issue Macro

Still need help?

The Atlassian Community is here for you.

Ask the community

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.

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.

Last modified on Nov 1, 2018

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.