- 
    
Bug
 - 
    Resolution: Deployed
 - 
    
High
 - 
    5.0 - EAP, 4.4.4
 - 
    None
 
- 
        4.04
 - 
        
 
Steps to reproduce:
- Take a custom field of type Select List (com.atlassian.jira.plugin.system.customfieldtypes:select).
 - Add an option to it that is invalid if parsed as XML. Example:
<FONT COLOR="#009900">Normal</FONT><img src="/images/icons/priority_minor.gif" >
 - Set this option as a value of this custom field to some issue.
 - Open XML view.
 
Observe: XML fails to be parsed, because the generated XML does not escape the option into CDATA section.
XML looks like
                  <customfield id="customfield_10540" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                    <customfieldname>[cf]Priority</customfieldname>
                    <customfieldvalues>
                      <customfieldvalue key="10560">
                        <FONT COLOR="#009900">Normal</FONT>
                        <img src="/images/icons/priority_minor.gif">
                      </customfieldvalue>
                    </customfieldvalues>
                  </customfield>
Expected: custom field value is wrapped into CDATA.
Note that "Multi Select" and "Multi Checkboxes" custom fields wrap their values into CDATA.
Reproducible on JIRA 5.0rc1.
- is duplicated by
 - 
                    
JRASERVER-25402 Ampersands (&) in custom field values can causes error with Issue Navigator XML view
-         
 - Closed
 
 -         
 
- relates to
 - 
                    
JRASERVER-23185 Not well-formed XML produced by XML view when a user with "&" in the name is set as a value of a User Picker custom field
-         
 - Closed
 
 -