Move an issue 1
Knowledge base 1
- Anonymous usage statistics 1
- Archived date functions 1
- Automation for Jira vs Jira Service Management automation 1
- Converting legacy rendering 1
- Jira Service Management compatibility 1
- Move an issue 1
- Permissions for project automation 1
- Solve unknown fields error in the audit log 1
- Transition an issue 1
On this page
Related content
- Move an issue
- Automation For Jira - Automation rule templates
- Getting the right version
- Concepts
- Automation For Jira - How to write a rule that moves issues to the Epic issue type from a different type
- Working with related issues
- How to clear a custom field value through an automation rule during issue clone
- Synchronize parent and sub-tasks issues
- Synchronize parent and sub-tasks issues 1
- Common use cases
While Jira has an option to move an issue to another project, this service isn't available to plugins or integrations like Automation for Jira Server.
The best workaround is to clone the issue and delete the original:
- Add a 'Clone issue' action and select the project you want to move the issue to. Automation for Jira Server will do its best to clone as many of the existing fields as possible, but items such as attachments do not move with the issue.
- Add a 'Delete issue' action to safely delete the original issue.
Last modified on Jun 24, 2020
Related content
- Move an issue
- Automation For Jira - Automation rule templates
- Getting the right version
- Concepts
- Automation For Jira - How to write a rule that moves issues to the Epic issue type from a different type
- Working with related issues
- How to clear a custom field value through an automation rule during issue clone
- Synchronize parent and sub-tasks issues
- Synchronize parent and sub-tasks issues 1
- Common use cases
Powered by Confluence and Scroll Viewport.