-
Suggestion
-
Resolution: Unresolved
-
None
-
0
-
Allow the "Then" actions in Jira to move issues to other projects.
I have multiple situations where the Jira Automation is able to detect instances where certain issues will be handled in other projects, but cannot move them there.
***
Problem
When an issue is moved between projects, the request type is lost and the request type can't be edited while moving the ticket. This causes problems with communication with customers.
Suggested resolution
Add the "Issue Moved" trigger and action in the automation rules.
Workaround
- is duplicated by
-
AUTO-218 Action to move an issue from one project to another (or change sub-task parent) - Cloning issues does not provide option to select parent issue when using sub-task issue types [Jira API constraint]
- Closed
-
AUTO-601 Add automation trigger and action for Move Issue
- Closed
-
JSDCLOUD-8570 Add "Issue Moved" in automation rule triggers
- Closed
-
JSWCLOUD-22679 New Automation action to move issues between projects
- Closed
- is related to
-
AUTO-551 Issue workflow/field configuration migration in automation
- Closed
- relates to
-
AUTO-551 Issue workflow/field configuration migration in automation
- Closed
-
JSWCLOUD-22679 New Automation action to move issues between projects
- Closed
-
JIRAAUTOSERVER-244 Action to change sub-task parent (or move a sub-task for one project to another)
- Gathering Interest
-
JSDSERVER-3511 Issue workflow/field configuration migration in automation
- Gathering Interest
This is a must have. Any update on when it might be addressed?