You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Hi all,
We are having some requests to migrate team-managed to company-managed projects. The problem is that the projects have this development Git Hub integration and we don't want to loose data. As you can predict the issue keys can't be the same in the destination project, so does anyone knows if there is some tip, trick or any workaround how we can perform the migration without loosing the links to GitHub in the Jira tickets?
Cheers,
Magdalena Zhisheva
Magdalena,
I am about to check if this works, but seems right:
https://community.atlassian.com/t5/Jira-Software-questions/If-I-move-Jira-issues-from-one-project-to-another-what-will/qaq-p/1241343
Out of interest did you hit any issues with this - just about to do the same and it would be useful to know.
Thanks
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.