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

Prevent duplicate field creation

XMLWordPrintable

    • 45
    • 104

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

      NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.

      Atlassian Update: Oct 2023

      Hi everyone,

      Thank you for your interest in this feature. As always, we highly value your feedback and suggestions. Our roadmap is shaped through inputs from multiple sources and jira.atlassian.com is one of them. At this stage, we are not planning to prioritise this suggestion, and will be transitioning this ticket to "not being considered".

      We understand our decision may be disappointing. Please reach out if you have any questions.

      Regards

      Carol (clow@atlassian.com)

      Product Manager, Jira Cloud

       

      Problem Definition

      Currently in JIRA, users can create duplicate custom fields. This is a problem because if a user creates a custom field with the same name as a default JIRA field and adds it to screens, it can make reporting in JIRA and in Portfolio inaccurate. An example field is Story Points. A user could create any number of Story Points fields and associate them with screens, but Portfolio will only read the field with the default field ID and thus, Story Points will not populate in Portfolio.

      Duplicate fields can also cause other issues and confusion for site administrators.

      Suggested Solution

      Prevent users from creating duplicate custom fields or at the very least display warning messages about custom fields being created with the same name as default JIRA fields.

      An issue could arise where this solution would prevent users from importing projects because their projects have the same field name as a field already in existence in the destination instance. This could be worked around by renaming those fields in the source instance.

              684cb16ed833 Carol Low
              rfuerst Rachel Fuerst (Inactive)
              Votes:
              97 Vote for this issue
              Watchers:
              78 Start watching this issue

                Created:
                Updated: