A4J: When 'Epic Link' field is selected on Edit issue action, then the Epic search jql is hardcoded to use 'type=Epic'

XMLWordPrintable

    • Severity 3 - Minor
    • 0

      Issue Summary

      When 'Epic Link' field is selected on Edit issue action, then the Epic search jql is hardcoded to use 'type=Epic'

      Steps to Reproduce

      1. Rename issue type Epic's name to a different name (including all next-gen/team-managed project issue types)
      2. Create automation rule and set action to 'Edit issue' and select 'Epic Link' field.
      3. Try to set a specific Epic by clicking on 'This field will be cleared' box

      Expected Results

      Epics will be listed

      Actual Results

      Epics aren't listed because the issue type name is changed.
      Below is the query used by the product, but you can see the issue type name is hardcoded to 'Epic'
      https:/<SITENAME>.atlassian.net/rest/api/2/search?fields=summary&jql=type%3DEpic

      Workaround

      Use Advanced field editing instead:
      https://support.atlassian.com/cloud-automation/docs/advanced-field-editing-using-json/

            Assignee:
            Unassigned
            Reporter:
            Yuji Sakai (Inactive)
            Votes:
            2 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: