How to retain merge request and Git data when moving Jira work items?

[Julia Watson-Clarke]

Hello Atlassian Community,

I'm currently in the process of bulk-moving tickets from our Team-Managed Spaces to Company-Managed spaces (so we can fulfil a future site migration and not lose these Spaces).

However, when moving work items, the Development  'Branches' and 'Merge Requests' logged in GitKraken are lost (I believe because these are linked to the Issue Key which is unique to each Space.

Has anyone got any advice on how best to bring over the linked Git data between Spaces?

Thanks,

Julia.

[David Nickell · Accepted solution]

I am not familiar with GitKraken.  But 1/2 of your answer may be in the the history table of your work items.

If you can get a list of "oprhaned" git Kraken Ticket Keys, then you can use that to find the new items.   If you go one by one scripted, perhaps you can script updates in GitKracken as well?  

An Example:   

• I just moved CSP1-16 to DEV-11 in my instance.
• This move is captured in your work item history (and other Atlassian indexes I believe).
• You can search on the old item to get the new item info through the UI
• Or, you can do this mechanically with the search REST Endpoint

How to take the matched keys and update gitKraken would take someone familiar with that tool 

---

Screenshot one -- the moved item detail is captured in Changelog

---

---

Screenshot two -- I can search for the moved item using the original key or the new key

[Julia Watson-Clarke]

Thanks @David Nickell ,

That's a good shout. I checked the History / Git Commits of the moved tickets but unfortunately the Git data hasn't been carried over with the moved ticket.

Back to the drawing board! Thanks anyway.

[David Nickell]

Thank you....  Just re-read your comment ... its a bit early for me so I think you've followed my dead-end to its logical conclusion  :-)

Good luck