Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

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

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.


1 answer

0 votes
Fabio Racobaldo _Herzum_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 01, 2022

Hi @Apryl Harris ,

in order to move a project from team-managed to company-managed you should follow this guide

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,


Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events