Details
-
Bug
-
Resolution: Duplicate
-
Low
-
Severity 3 - Minor
-
Description
Issue Summary
Clone actions fail to create issues if the current issue is a subtask and the target is non-subtask
Steps to Reproduce
- Create an automation rule that would clone a subtask as a non-subtask (Bug,story, etc) on the same project or a different project based on any trigger.
Expected Results
The issue should be cloned as a non-subtask in the same project or a different project.
Actual Results
Automation fails to clone the issue with the following errors:
When cloning on the same project:
Given parent issue does not belong to appropriate hierarchy (parentId)
When cloning to a different project:
Sub-tasks must be created in the same project as the parent. (project)
Workaround
Add the following to the advanced section of the clone issue action:
{ "fields": { "parent": null } }
Attachments
Issue Links
- is duplicated by
-
JSWCLOUD-22457 Clone actions fail to create issue saying Parent issue is needed even though target issue is non-subtask
- Closed
-
JSWCLOUD-22914 Clone actions for Epic issue types fails to create issue saying "cannot have Parent but parent is specified"
- Closed