-
Bug
-
Resolution: Fixed
-
Highest
-
18
-
Minor
-
14
-
Issue Summary
A column disappears unexpectedly in the Jira issue macro on Confluence pages if a Column is using a Jira custom field with duplicate name and different context.z
We can observe that although the macro preview shows the correct value, the source code shows that all custom fields with the same name have been selected for the same column.
For instance:
properties":\{"columns": [\{"key":"issuetype"\}, \{"key":"key"\}, \{"key":"summary"\}, \{"key":"status"\}, \{"key":"resolutiondate"\}, \{"key":"customfield_10001,customfield_10124"\}]\} <= it should only have customfield_10124
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 from Global to the specific project - So, dupFields checkbox with context to the project "Test1" and dupFields Selection list with context to the project "Test2";
8. Refresh Confluence page
Expected Results
No changes, the dupFields column is still visible.
Actual Results
- The column is no longer visible
- Using the view mode, when reaching the "Columns" icon, we can observe that the Custom Field is checked. Observe that when we opened this Columns window, the column "dupFields" was visible again. If we refresh the results, the column disappears again.
- Using the edit mode, when reaching the "Columns" icon, we can observe that the Custom Field is checked. Observe that when we opened this Columns window, the column "dupFields" was visible again. if we run the search, the column disappears.
Workaround
- Use Jira Legacy Macro. Select both dupFields and observe which column returned value;
- Remove the other dupFields that did not show values.
- relates to
-
CONFCLOUD-81084 Column is empty in Jira Issue Macro when there are duplicate custom field names
-
- Closed
-
-
CONFCLOUD-71285 Jira custom fields with a duplicate names to system fields or other custom fields cannot be rendered
-
- Closed
-
-
CONFCLOUD-80785 Confluence database jira custom field value is not showing up
-
- Closed
-
-
CONFCLOUD-80376 Disappearing Column in Jira Issue Macro depending on the context of the field
-
- Closed
-
- depends on
-
EDM-11830 Loading...