The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

How to make a bulk move with over 1000+ issues without breaking the links?

Apryl Harris
April 19, 2022

I have project that needs to move from team to company managed. Many of the projects have over 1000+ issues. How can I move those without breaking the hierarchy links? Is there a specific JQL you can suggest to to segregate the issues and their related issues?

Please advise.

Thanks.

1 answer

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

0 votes
Fabio Racobaldo _Catworkx_
Community Champion
May 1, 2022

Hi @Apryl Harris ,

in order to move a project from team-managed to company-managed you should follow this guide https://support.atlassian.com/jira-service-management-cloud/docs/migrate-between-next-gen-and-classic-projects/

When you move an issue the old key will continue to work because jira store the old issue key. Based on that links should continue to work after migration. Please test this on a subset of issues first even if they should work.

Hope this helps,

Fabio