Issue Summary

This is reproducible on Data Center: (yes) 

A global issue has been identified in the customer instance (v10.3.18), where Component names containing an ampersand (&) are incorrectly rendered as &.

This error is causing a failure of custom fields logic. A custom field is configured to populate based on the selected Component. Because the system is using & instead of &, the custom field fails to recognize the component match.

Steps to Reproduce

1. Create a new "Component" with name "RF & TEST"

1. Create a new issue and click to expand the Component Drop down

1. The new component is listed as RF & TEST, instead of RF & TEST when we create new issues or reuse it in any logic with other custom fields.

Expected Results

1. When creating issues and trigger the Component drop down we should load components with "&" instead "&"
2. When automatically populate custom fields based on selected component, we should populate the same value instead of display a blank option and force us to manually select it after creating the issue.

Actual Results

• Components are wrongly displaying "&" when we select it in the create issue screen
• If we create a logic to populate other custom fields based on the component it will not load automatically.

Workaround

For this custom field reusage logic, user can manually select the Compoment used while creating the issue.