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

Creating a custom field the same name with a system field breaks JQL that relies on the system field

XMLWordPrintable

      Issue Summary

      If a custom field (either global or team-managed) is created named as Epic Link, that will break all functionalities that use to query the field the Epic Link field, such as the feature to view all issues under an Epic:

      • In that case, that field is a text field

      The same issue happened for other fields , such as :-

      • Request Type

      Steps to Reproduce

      • Create a text field named as Epic Link (either a global field or a Team-managed one)
      • Perform a JQL with "Epic Link =" for company-managed issues that have an epic link
        • Or click to view all issues within an Epic

      Expected Results

      Either JQL should only utilize the system field "Epic Link" or the admin of the team-managed project should not be allowed to use the name "Epic Link"

      Actual Results

      JQL no longer works and previously saved filters with "Epic Link" will fail . The error return as :-

      The operator '=' is not supported by the 'XXXX' field.
      

      Workaround

      The team-managed field needs to be removed or rename. In order to locate the project in which it resides, admins need to contact Atlassian Support.

      An alternative workaround is to replace in JQL the expression "Epic Link=" with "cf[<the id of the field>]=. For example: "cf[10004]="

              kpainter@atlassian.com Kyle Painter
              clionte Claudiu Lionte (Inactive)
              Votes:
              2 Vote for this issue
              Watchers:
              12 Start watching this issue

                Created:
                Updated:
                Resolved: