Loading...

XML

Word

Printable

Type: Suggestion
Resolution: Unresolved
Component/s: Administration - Deprecated, Global Administration - Fields, Issue Types, Screens, Schemes and Priorities
Labels:
- RIBS-Long

UIS:
108
Support reference count:
97
Feedback Policy:

Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

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

https://community.atlassian.com/t5/Jira-discussions/JIRA-field-with-same-name-Duplicate-Field-names/td-p/693235

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...

mentioned in: Page Loading...; Page Loading...

(3 is related to, 2 relates to, 1 was cloned as, 1 is addressed by, 2 mentioned in)

Assignee:: Unassigned

Reporter:: Girish Jagdale

Votes:: 91 Vote for this issue

Watchers:: 63 Start watching this issue

Created:: 25/Dec/2017 6:04 AM

Updated:: 3 days ago 2:09 AM

Details

Description

Attachments

Issue Links

Forms

Activity

People

Dates