Automation for Jira - Writing a rule to move an issue to another project
Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms.
Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
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 May 30, 2024
Powered by Confluence and Scroll Viewport.