Originally asked by David Loszewski on 03 November 2021 (original question)
I just started using Exalate, I have a sync setup between to instances, do the issues at the destination instance need to already exist for the sync to work? The sync I currently have setup didn’t seem to create any issues when I ran the sync.
Comments:
David Loszewski commented on 04 November 2021
To provide clarity for my use case…I’m currently trying to migrate a project from one Jira instance to another. ie. destination will be abc.atlassian.net and source will be xyz.atlassian.net
The problem is that the source project needs to remain intact and in use until I can make sure that all issues are migrated over correctly and permissions are correct, which is where exalate comes into play. I was going to migrate all issues over to a project of the same name in site abc while the developers are still making changing to issues in site xyz. So exalate would then sync over all and any changes made to the xyz issues to abc issues.
So I’m starting off with a blank project in abc, and was looking for a way to move over all issues from xyz to abc while maintaining the original ticket numbers and creation dates/times. I thought I might be able to do with with a sync but when I kick off a sync it just spins, says completed, and that’s it, no issue creation has taken place. So I’m concerned that even if I move tickets over manually using something like DeepClone or cloud migration how would I know that any new issues in xyz would also be created in abc?