Move an issue
Knowledge base
- Anonymous usage statistics
- Archived date functions
- Automation for Jira vs Jira Service Management automation
- Converting legacy rendering
- Expire audit log items
- Integrate Microsoft Teams
- Integrate Slack
- Jira Service Management 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
- View performance insights
- Setting configuration properties
On this page
Related content
- Automation for Jira vs Jira Service Management automation
- Automation for Jira vs Jira Service Management automation
- Getting the right version
- Working with related issues
- Triggers
- Automation For Jira (A4J) Data Center - The ultimate troubleshooting guide
- Automation For Jira - Automation rule templates
- Common use cases
- Reference
- How to use Automation for Jira sample rules in your project
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 Apr 21, 2021
Related content
- Automation for Jira vs Jira Service Management automation
- Automation for Jira vs Jira Service Management automation
- Getting the right version
- Working with related issues
- Triggers
- Automation For Jira (A4J) Data Center - The ultimate troubleshooting guide
- Automation For Jira - Automation rule templates
- Common use cases
- Reference
- How to use Automation for Jira sample rules in your project
Powered by Confluence and Scroll Viewport.