Uploaded image for project: 'Jira Platform Cloud'
  1. Jira Platform Cloud
  2. JRACLOUD-68370

Prevent users from creating custom fields using the same name as an existing system or custom field

XMLWordPrintable

    • 259
    • 111

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

            [JRACLOUD-68370] Prevent users from creating custom fields using the same name as an existing system or custom field

            SET Analytics Bot made changes -
            Support reference count Original: 110 New: 111
            SET Analytics Bot made changes -
            UIS Original: 244 New: 259
            SET Analytics Bot made changes -
            UIS Original: 243 New: 244

            Ramsi Hawkins added a comment -

            7c134b43cfa4: The EXACT thing Judy explained happened in my org a couple months ago. Another example, someone created a custom field named "Rank" so every filter in the company that was set up to "ORDER BY Rank ASC" no longer had a valid rank field. Every Board in the company that used stack ranking (hundreds of them) stopped being able to drag and drop tickets to change priority order.

            Ramsi Hawkins added a comment - 7c134b43cfa4 : The EXACT thing Judy explained happened in my org a couple months ago. Another example, someone created a custom field named "Rank" so every filter in the company that was set up to "ORDER BY Rank ASC" no longer had a valid rank field. Every Board in the company that used stack ranking (hundreds of them) stopped being able to drag and drop tickets to change priority order.
            SET Analytics Bot made changes -
            UIS Original: 239 New: 243
            SET Analytics Bot made changes -
            UIS Original: 241 New: 239
            SET Analytics Bot made changes -
            UIS Original: 214 New: 241
            SET Analytics Bot made changes -
            Support reference count Original: 109 New: 110
            SET Analytics Bot made changes -
            UIS Original: 213 New: 214
            SET Analytics Bot made changes -
            UIS Original: 200 New: 213

              Unassigned Unassigned
              a1db914806ea Girish Jagdale
              Votes:
              101 Vote for this issue
              Watchers:
              75 Start watching this issue

                Created:
                Updated: