Issue Summary

Similar to CONFCLOUD-80466, when the correct custom field is using global context and there are duplicated custom fields with context defined to other Projects, the column is not populated.
Source code shows that all custom fields with the same name have been selected for the same column:

...
"views":[{"type":"table",
"properties":{"columns":
[{"key":"key"},
{"key":"summary"},
{"key":"customfield_18280","width":127},
{"key":"customfield_14762","width":110},
{"key":"customfield_18273"},
{"key":"customfield_18277","width":98},
{"key":"customfield_15682,customfield_18939,customfield_19456"}] ===> Multiple fields
}}]}"">
...

Steps to Reproduce

1. Create two custom fields with the same name, for instance "dupField" One may be a selection list, and the other a checkbox;
2. The checkbox was added to the screens used by project "Test1", the Selection list for the project "Test2";
3. Create some issues for the 'Test1" project, with values for the "dupField";
4. In Confluence, create a new page and add the Jira Issues Macro;
5. Use a JQL to select issues from the "Test1" project, and select the "dupField" column;
6. Publish the page, observe that the column "dupField" is correct;
7. In Jira, edit each "dupField" and change the context. Keep Global for checkbox, and the selection list with context to the project "Test2";
8. In Confluence, add the Jira Issues Macro and use the same JQL used on step 5. Select the "dupField" column.

Expected Results

No changes, the dupFields Column shows valid content

Actual Results

• The column does not show values.

Workaround

• Use Jira Legacy Macro. Select both dupFields and observe which column returned value;
• Remove the other dupFields that did not show values.