Note: This is a break down of https://jira.atlassian.com/browse/JSDCLOUD-10516 to cover all possible fields we create on behalf of customers.

Custom fields impacted from Change Management features:

• Change Type
• Change Risk
• Change Reason
• Implementation Plan
• Backout Plan
• Test Plan
• Change Start Date
• Change Completion Date
• Planned Start Date
• Planned End Date

Issue Summary

This is reproducible on Data Center: no

Steps to Reproduce

1. Create a custom field called `Change Type`
2. Create a new ITSM project

Expected Results

• There is only one `Change Type` custom field OR the duplicate custom fields do not break automation: https://jira.atlassian.com/browse/AUTO-161

Actual Results

• There are duplicate `Change Type` custom fields AND they break automation: https://jira.atlassian.com/browse/AUTO-161

Workaround

• Delete the personally created `Change Type` field and keep the system created field.

NOTE: You can replace `Change Type` field with any of the change fields at the top.