-
Bug
-
Resolution: Unresolved
-
Low
-
None
-
5.7.3
-
JIRA 6.3.14
-
1
-
Severity 3 - Minor
-
0
-
Repro:
- Name a field XYZ in all caps.
- Pull in issues using jiraissues macro. Select XYZ field.
- The field is rendered as Xyz in the headings of the JIRA issues macro. Expected result should be XYZ.
- relates to
-
CONFSERVER-34016 JIRA Issues Macro should respect the case of custom JIRA Fields
- Gathering Interest
- mentioned in
-
Page Failed to load
[CONFSERVER-38124] jiraissues macro not preserving the case of JIRA field names
UIS | Original: 1 | New: 0 |
UIS | New: 1 |
Support reference count | New: 1 |
Workflow | Original: JAC Bug Workflow v3 [ 2878905 ] | New: CONFSERVER Bug Workflow v4 [ 3002774 ] |
Workflow | Original: JAC Bug Workflow v2 [ 2783706 ] | New: JAC Bug Workflow v3 [ 2878905 ] |
Workflow | Original: JAC Bug Workflow [ 2712296 ] | New: JAC Bug Workflow v2 [ 2783706 ] |
Symptom Severity | Original: Minor [ 14432 ] | New: Severity 3 - Minor [ 15832 ] |
Workflow | Original: Confluence Workflow - Public Facing - Restricted v5 - TEMP [ 2384473 ] | New: JAC Bug Workflow [ 2712296 ] |
Status | Original: Open [ 1 ] | New: Gathering Impact [ 12072 ] |
Workflow | Original: Confluence Workflow - Public Facing - Restricted v5 [ 2279213 ] | New: Confluence Workflow - Public Facing - Restricted v5 - TEMP [ 2384473 ] |
This issue still exists in current Confluence versions. Product owners and users want reports that correctly display column names (ie. Jira field names) that they have purposefully formatted per requirements. How about an update and revisit on this bug, Atlassian?