I am offboarding a client and they would like their entire Jira project to include comments, links, attachments, etc. I was initially going to export all of their tickets with all of the fields to a .csv file but noticed the attachments and links aren't part of that.
Any suggestions in regards to that as well as the case where I have tickets that are part of a larger project? Would I just need to filter those issues since not all of the info pertains to that particular client?
Welcome to the Community!!
Well we have migration, which migrates most metadata
https://support.atlassian.com/migration/docs/perform-a-cloud-to-cloud-migration-for-jira
Let me know if you have any queries on this
Thanks,
Pramodh
Thanks for the quick response. So if I'm reading the instructions correctly I would need to know the following:
1. admins for the source site and the destination site. Is it alright that the destination site is an entirely separate organization altogether? Does the receiving organization need to add my IT (source site admin) as a destination site admin in order to perform the migration?
2. Need to know the details of the destination site
Is there anything else I am forgetting?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes separate organization is also allowed,
It's better that whoever is performing the migration is added as site ad min in destination site as well
Testing the migration and recording the steps will be important aspect here!
Thanks
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Welcome to the community, @Laurie Amagan.
I am Marlene from codefortynine.
Another option would be to bulk clone all issues of the project to the Jira cloud instance of your former customer. This is possible with our app Deep Clone for Jira.
The Instance Clone is pretty simple to perform and we offer a lot of setting options. So you are free to decide which content you want to clone.
The main work would be to set up the target project and make sure that all fields are available that should be cloned from the source issues.
You can read more about migrating issues with Deep Clone for Jira in our documentation.
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.