Move an issue
Knowledge base
- Anonymous usage statistics
- Archived date functions
- Automation for Jira vs Service Desk automation
- Converting legacy rendering
- Expire audit log items
- Integrate Microsoft Teams
- Integrate Slack
- Jira Service Desk compatibility
- Move an issue
- Optimize rules
- Organize your rules with labels
- Permissions for project automation
- Service limits
- Solve unknown fields error in the audit log
- Transition an issue
On this page
Related content
- Automation For Jira - Automation rule templates
- Automation For Jira - How to write a rule that moves issues to the Epic issue type from a different type
- Getting the right version
- Actions
- Concepts
- Automation for Jira - Writing a rule that clones stories (and their sub-tasks) linked to an Epic when the Epic is cloned
- How to clear a custom field value through an automation rule during issue clone
- Automation Error: Could not find create meta data for project/typeId
- How to copy the field values to the destination issue when an issue is split in the backlog?
- Destination Project Missing in Drop-Down During Bulk Change in Jira Cloud
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
- Automation For Jira - Automation rule templates
- Automation For Jira - How to write a rule that moves issues to the Epic issue type from a different type
- Getting the right version
- Actions
- Concepts
- Automation for Jira - Writing a rule that clones stories (and their sub-tasks) linked to an Epic when the Epic is cloned
- How to clear a custom field value through an automation rule during issue clone
- Automation Error: Could not find create meta data for project/typeId
- How to copy the field values to the destination issue when an issue is split in the backlog?
- Destination Project Missing in Drop-Down During Bulk Change in Jira Cloud
Powered by Confluence and Scroll Viewport.