-
Bug
-
Resolution: Fixed
-
Low
-
7.4.3, 7.6.2
-
1
-
Severity 3 - Minor
-
Problem
In a Confluence site version 7.4.x or 7.6.x connected to a Jira Software via an application link.
We cannot add 2 Jira custom fields as columns to display in a Jira Issue Macro (table view) due to case-sensitivity.
Environment
Confluence version 7.4.x or 7.6.x connected to a Jira Software version 8.4.2 via an application link
Steps to Reproduce
- Create 2 custom fields in Jira and configure them to be displayed on some default screens for the user to fill in. In our example, we called these fields end date and End date and they were date pickers.
- Create a new Jira Issue / Bug and assign a new value to these fields
- Go to Confluence and create a new Confluence page adding a Jira Issue Macro
- Customize the Jira Issue Macro and try to make the new custom fields displayed as a column in a Table view
Expected Results
The user can pick the 2 custom fields as columns to display in a Jira Issue Macro
Actual Results
After picking the first custom field, the second one becomes unavailable for selection in the Jira Issue Macro
Workaround
No Workaround at this stage except renaming fields on the Jira side that may not be convenient for the user needs.
Notes
A video is attached with my steps to reproduce in Confluence
- duplicates
-
CONFSERVER-54959 JIRA Issue Macro doesn't differentiate custom fields with different casing
- Closed
- relates to
-
CONFSERVER-57785 Jira Issue Macro doesn't distinguish multiple custom field with same name in "Columns to display"
- Closed