-
Suggestion
-
Resolution: Unresolved
-
138
-
91
-
While creating custom field, it is not checked if field with same name already exist in default or custom field. This allow Admin to create duplicate field and causes confusion when that field is needed to be added in screen or reports, as which one to use.
Refer user feedback on this from community
A feature is required that checks and stops Admin from creating such field.
- duplicates
-
JRACLOUD-75022 Stop Allowing Custom Field created with same name as existing default field or custom field
- Closed
- is duplicated by
-
JRACLOUD-80592 Ability to make any required issue field unique
- Closed
-
JSWCLOUD-18756 Restrict Team-Managed custom fields name if already exists another custom field with the same name
- Gathering Interest
- is related to
-
JRACLOUD-76913 Changing Language settings allows duplication of the system fields Summary and Description
- Closed
-
JRACLOUD-67591 Jira allows admins to create custom fields with the same name
- Closed
-
JRACLOUD-74037 Issue search should distinguish between custom fields that have the same name
- Gathering Interest
-
JSWCLOUD-23749 Search needed for all custom fields across TMP and CMPs
- Gathering Interest
-
JRACLOUD-61376 Prevent duplicate field creation
- Not Being Considered
- relates to
-
JRACLOUD-79586 Creating a custom field with a duplicate name will break saved filters
- Closed
-
JRASERVER-61376 Prevent duplicate field creation
- Gathering Interest
- was cloned as
-
JRACLOUD-75022 Stop Allowing Custom Field created with same name as existing default field or custom field
- Closed
- is addressed by
-
ENT-2311 Loading...