How to move a project to another project not just the issues, but also the automation and the Jira ticketing
Replicate Workflows: Manually recreate the workflows from the old project in the new one. You can copy workflows from the old project and apply them to the new project.
Replicate Automation Rules: Manually recreate the automation rules from the old project. Go to Project settings
> Automation
, and set up the rules as they were in the old project.
Copy Custom Fields and Screens: Ensure that any custom fields, screens, and field configurations are copied to the new project.
Permissions and Notifications: Configure the new project’s permissions and notification schemes to match those of the old project.
Bulk Change
> Move Issues
.Several Jira Marketplace add-ons can help with project migration. These tools often provide more streamlined processes for moving projects, including configurations:
Would that break any automation that are running on the receiving project?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Broderick Prewitt It won't break any automation but mapping is more important. And we can get export and import automation options also in admin panel.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Will it work the same way if I want to move a project from one team to another?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.