Issue Summary

Currently, certain fields in Jira Cloud are locked because they are integral to the system's functionality. While we understand the importance of these fields, there are scenarios where organizations need to customize their field names or remove unused fields to better align with their business processes and naming conventions.

Proposed Solution:

• Allow administrators to rename locked system fields while maintaining their core functionalities.
• Provide an option to safely delete or archive unused system fields, ensuring that any dependencies or critical functions are not disrupted.

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available