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

Jira should store the custom field details based on field ID instead of the field name

    XMLWordPrintable

Details

    • 1
    • 11

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

    Description

      When we save a filter that includes a custom field, Jira should save the field based on its id rather than the name of the filter.

      For now, if we rename a field, it will break all the Filters, Automation Rule when the Field is in use.

      How this is going to benefit us:

      1. Saving a filter using the filed name, if we rename the field, we get the error - "Field 'alpha' does not exist or you do not have permission to view it."

      2. If we use, field ID -> example cf[10131] is not empty , this continues to work even if we rename the field.

      Attachments

        1. Field Name.png
          Field Name.png
          48 kB
        2. screenshot-1.png
          screenshot-1.png
          149 kB
        3. screenshot-2.png
          screenshot-2.png
          146 kB
        4. Screenshot 2021-04-21 at 5.48.18 AM.png
          Screenshot 2021-04-21 at 5.48.18 AM.png
          39 kB
        5. screenshot-3.png
          screenshot-3.png
          99 kB

        Issue Links

          is cloned from

          Suggestion - JRACLOUD-61048 As a jira admin asked to rename a custom field, I want to know which filters contain the custom field, so I know which ones to update

          • Gathering Interest
          is related to

          Bug - A problem which impairs or prevents the functions of the product. JRACLOUD-83050 Duplicate Custom Field Names in Team Managed Project is causing issues with JQL results

          • High - High priority issues
          • Closed

          Suggestion - JRACLOUD-79983 [Tracking in issue links] Various issues related to actions that cause broken Saved Filters

          • Gathering Interest
          relates to

          Bug - A problem which impairs or prevents the functions of the product. JRACLOUD-79586 Creating a custom field with a duplicate name will break saved filters

          • High - High priority issues
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. JRACLOUD-79587 Deleting a custom field will break saved filters

          • Low - Low priority issues
          • Gathering Impact

          Suggestion - JRACLOUD-74535 Administrative mass modify of filter constants

          • Closed

          Suggestion - AUTO-468 Support for field IDs instead of just field names in Automation

          • Gathering Interest

          Suggestion - JRACLOUD-30467 Renaming a project or issuetype breaks filters saved with the old project or issue type name

          • Gathering Interest

          Suggestion - JRACLOUD-77880 Renaming a version breaks all related filters

          • Gathering Interest

          Activity

            People

              Unassigned Unassigned
              ssingh7@atlassian.com Sugandha Singh
              Votes:
              15 Vote for this issue
              Watchers:
              10 Start watching this issue

              Dates

                Created:
                Updated: