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

Creating a custom field with same name and context as another custom field leads to error in Advanced search

XMLWordPrintable

      Issue Summary

      Creating a duplicate custom field with the same name as another custom field of different type will lead to error in advanced search.

      Steps to Reproduce

      1. Create a custom field of type Text-multiline and name it as say "TestCustomField"
      2. Now add a context to this custom field with issue type and project.
      3. Create another custom field of type Select list multiple choice , with same name , say , "Testcustomfield" and add the same context as the previous one.
      4. Assign these two custom fields to screens in that project.
      5. Now proceed to search for issues in that project in Advanced search.
      6. When you choose the custom field "Testcustomfield" ( which is a select list ) and perform the JQL search , it returns an error stating " The operator '=' is not supported by the 'Testcustomfield' field.

      Expected Results

      It should identify the proper custom field

      Actual Results

      The search is getting confused with the another custom field with same name which is Text multi line , where it does not support = operator.

      Workaround

      • Rename one of the custom field
      • Perform advanced search using the custom field ID.

        1. 2-values.png
          84 kB
          Uchechi I
        2. Screenshot 2020-04-16 at 6.21.02 PM.png
          79 kB
          Vijay U
        3. Screenshot 2020-04-16 at 6.23.17 PM.png
          99 kB
          Vijay U
        4. Screen Shot 2022-08-25 at 12.48.26 pm.png
          28 kB
          Jordan Koukides
        5. Screen Shot 2022-08-25 at 12.48.43 pm.png
          40 kB
          Jordan Koukides

              Unassigned Unassigned
              vujjannavar@atlassian.com Vijay U
              Votes:
              4 Vote for this issue
              Watchers:
              20 Start watching this issue

                Created:
                Updated:
                Resolved: