Issue Summary

Jira issues macro does not work correctly with two homonymous global custom fields.

Steps to Reproduce

• Create a global custom field (e.g. test)
• Create a second global custom field with the same name (e.g. test)
• Add the custom field to the Jira issue (only one "test" will be visible in the Jira issue field configuration)
• Set a value for "test"
• Add "test" as a column in the Jira issues macro in Confluence.

Expected Results

The column "test" will have the expected values.

Actual Results

The column "test" will have blank values.

Workaround

Having different names for custom fields in Jira seems to prevent such problems.