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
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
I am planning a merge of one JIRA Cloud instance to another. I have opted to import through CSV. The instructions note to recreate the project and setup the project configurations on the target site. I have setup everything in the target instance but wonder if I need to also setup the 'Releases' in the target site before migrating or will the releases be migrated during the import?
Hi Connie,
Hope this message finds you well! The CSV Methodology consists of pretty much exporting issues to a file to later import them on a different instance.
I am not familiar with the 'Releases' field though, assuming it is a field. Jira can manage releases through the usage of the Fix Version(s) and Affects Version(s) fields. If you need these imported, all you need to do is to ensure that they are selected as part of your JQL filter that will be exported to CSV to be later imported to another instance.
Now, if by 'Releases' you meant something else, I'd like to ask you to clarify where it exists by either sending a screenshot or explaining further so we can determine together whether that's migrated or not.
Looking forward to hearing from you!
Best,
Marcelo
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.