Details
-
Bug
-
Resolution: Fixed
-
High
-
13
-
Severity 3 - Minor
-
10
-
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
- Create a rule with the follow structure:
- Branch on subtasks
- 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
- duplicates
-
JSWCLOUD-22524 Clone actions fail to create issue if the current issue is a subtask and target is non-subtask
- Closed
- was cloned as
-
JSWCLOUD-22914 Clone actions for Epic issue types fails to create issue saying "cannot have Parent but parent is specified"
- Closed