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

JQL breaks with company-managed (formerly classic) custom fields if a team-managed (formerly next-gen) duplicate exists

    XMLWordPrintable

Details

    • Bug
    • Resolution: Answered
    • High
    • Search - Frontend
    • None

    Description

      Issue Summary

      If you create a custom field in a team-managed (formerly next-gen) Project and the name already exists in the company-managed (formerly classic) global custom fields, using the field in a JQL search will break, causing any existing filters using this field to fail.

      Note - The bug also impacts the JQL search in add-ons - e.g Slack integration, Teams, etc.

      Steps to Reproduce

      1. Create a custom field in the global system settings (company-managed (formerly classic))
      2. Create a custom field with the same name in a team-managed (formerly next-gen) Project

      Expected Results

      The JQL basic and advanced search should recognize these are 2 different fields and continue to function accordingly.

      Actual Results

      Any existing filters using the company-managed (formerly classic) version of the field will break and going forward you can only query this field by using a different syntax that includes the field type


      Workaround

      • Simply rename one of the custom fields so there are no duplicates
      • Use a different syntax for the field reference in your JQL which includes the field type (eg. "Chocolate[Number]")
      • Use the custom field id in the Advanced search instead of the custom field name

      Attachments

        Issue Links

          is related to

          Bug - A problem which impairs or prevents the functions of the product. JRACLOUD-74239 Creating a custom field with same name and context as another custom field leads to error in Advanced search

          • High - High priority issues
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. JRACLOUD-75408 Searching for custom fields that share name using JQL does not include all of the fields.

          • High - High priority issues
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. JRACLOUD-76482 Inaccurate JQL search results when using IS EMPTY operator with duplicate fields

          • High - High priority issues
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. AUTO-161 Automation fails when it has two fields with the same name/type, showing the error "Found multiple fields with the same name and type:"

          • Low - Low priority issues
          • Long Term Backlog
          relates to

          Bug - A problem which impairs or prevents the functions of the product. JRACLOUD-76536 JQL "custom field" is EMPTY does not work when there are other custom fields with the same name

          • Medium - Medium priority issues
          • Closed
          mentioned in

          Page Loading...

          Page Loading...

          Activity

            People

              Unassigned Unassigned
              lellis2@atlassian.com Belto
              Votes:
              10 Vote for this issue
              Watchers:
              29 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: