Background: In the current Jira Cloud configuration, Space Administrators for Team-Managed Spaces can create new custom fields directly in their Space settings.

The Problem: The system currently allows users to create new custom fields that share the exact same name as existing native system fields (e.g., "Labels", "Assignee", "Reporter") or existing global custom fields. There is no validation or warning prompt to prevent this exact string match.

Impact: When duplicate names are created, it causes significant configuration conflicts:

• Visual Duplication: Both the system field and the custom field can render simultaneously on the Work Item view/preview screens, causing confusion for end-users.

• Administrative Overhead: In the Work Item layout configuration screen, both fields appear with the exact same name, making it impossible for administrators to visually distinguish between the system field and the newly created custom field.

• Data Fragmentation: Users may tag or input data into the custom field instead of the system field, breaking global JQL filters and cross-Space reporting.

Suggested Solution: Implement a validation check when a user attempts to save a new custom field in a Team-Managed Space.

• Option A (Strict): Block the creation of the field if the name matches a native Jira system field, prompting the user to choose a unique name.

• Option B (Warning): Display a prominent warning stating that a field with this name already exists, advising the user that proceeding will cause layout and reporting conflicts.

Current Workaround: Jira Administrators must navigate to global Settings > Work Items > Custom fields, manually identify the unlocked custom fields, and rename them to establish distinct nomenclature before correcting the Space's Work Item layout.