Uploaded image for project: 'Jira Software Cloud'
  1. Jira Software Cloud
  2. JSWCLOUD-22457

Clone actions fail to create issue saying Parent issue is needed even though target issue is non-subtask

    XMLWordPrintable

Details

    Description

      Issue Summary

      When creating issues through Clone Action, the following error message is shown in audit log:

      Given parent issue does not belong to appropriate hierarchy (parentId) 

      Steps to Reproduce

      1. Create a rule with the follow structure:
      2. Branch on subtasks
      3. Clone issue (with target issue type as a non subtask)

      The problem also happens when trigger issue is from a level above Epic and if the rule tries to create an Epic level issue, even without any branch.

      Expected Results

      Since the rule is not creating a sub-task issue, no Parent ticket should be needed.

      Actual Results

      The rule fails even asking for a Parent issue to be set:

      Given parent issue does not belong to appropriate hierarchy (parentId) 

      Workaround

      Add the following to the Additional Fields section within the Clone Issue action:

      {
         "fields": {
            "parent": null
         }
      } 

      Attachments

        Issue Links

          Activity

            People

              andreask@atlassian.com Andreas Knecht (Inactive)
              itrojahn@atlassian.com Ilenice
              Votes:
              19 Vote for this issue
              Watchers:
              29 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: