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
- Checking URLs against the Jira allowlist
- 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
- How to troubleshoot Bamboo connectivity issues with Databases
- How to monitor long running Queries in Confluence using PgAdmin
- PostgreSQL segmentation fault after upgrading to Bitbucket 4.11 and up
- Bamboo fails to start after PostgreSQL migration with error relation build does not exist
- Database Troubleshooting
- How to fix the collation of a Postgres Confluence database
- Database Troubleshooting for PostgreSQL
- How to set up a basic PostgreSQL database for Hipchat Data Center
- Troubleshooting webhook security issues
- Blank HTML on all confluence pages, when applied the 9.4.2, 9.3.7, 9.2.11, 9.1.16 and/or 9.0.20 PostgreSQL updates
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 21, 2022
Related content
- How to troubleshoot Bamboo connectivity issues with Databases
- How to monitor long running Queries in Confluence using PgAdmin
- PostgreSQL segmentation fault after upgrading to Bitbucket 4.11 and up
- Bamboo fails to start after PostgreSQL migration with error relation build does not exist
- Database Troubleshooting
- How to fix the collation of a Postgres Confluence database
- Database Troubleshooting for PostgreSQL
- How to set up a basic PostgreSQL database for Hipchat Data Center
- Troubleshooting webhook security issues
- Blank HTML on all confluence pages, when applied the 9.4.2, 9.3.7, 9.2.11, 9.1.16 and/or 9.0.20 PostgreSQL updates
Powered by Confluence and Scroll Viewport.