- 
    
Bug
 - 
    Resolution: Fixed
 - 
    
High
 
- 
        11
 - 
        Minor
 - 
        6
 - 
        
 
Issue Summary
When Jira Custom Fields name contains a comma (,) or slash / Jira Legacy macro splits the Custom Fields name into different columns for each comma/slash.
Steps to Reproduce
- Create a Custom Field that has a comma or a slash in its name and add a value to the Custom Field


 - Insert Jira Legacy macro on a Confluence page and add the Jira project key of the issues you would like to display
 - In "Fields to Display", Include the created Custom Field that contains the comma/slash
 - Publish the page
 
Expected Results
The Custom Fields with a comma or a slash in their names are displayed as a single column and their values are correctly displayed.
Actual Results
The Custom Fields with a comma or a slash in their names are displayed in more than one column. Also, for the custom fields with a slash, it is added the '/' value.

Workaround
Currently, the available workaround for this scenario would be using the new Jira Issue instead of the legacy.
- is duplicated by
 - 
                    
CONFCLOUD-77305 Using a "/" in a Custom Jira field will prevent the content of the field to render in the Jira macro in Confluence
-         
 - Closed
 
 -         
 - 
                    
CONFCLOUD-77274 Jira Legacy macro breaks column and doesn't show values when field name contains slash characters "/"
-         
 - Closed
 
 -         
 
- relates to
 - 
                    
CONFCLOUD-75894 Jira Macro "Filter Results" does not show columns for Custom Fields (Jira) with comma in their names
-         
 - Gathering Impact
 
 -         
 
- mentioned in
 - 
                    
Page Loading...
 - 
                    
Page Loading...
 - 
                    
Page Loading...
 - 
                    
Page Loading...
 - 
                    
Page Loading...
 - 
                    
Page Loading...
 - 
                    
Page Loading...
 - 
                    
Page Loading...
 - 
                    
Page Loading...
 - 
                    
Page Loading...
 - 
                    
Page Loading...
 - 
                    
Page Loading...
 - 
                    
Page Loading...