Is there any way to map changesets to issues when migrating FogBugz-on-demand -> JIRA-on-demand and Kiln -> Bitbucket?
Repositiory and issue import work fine, new changesets are succesfully mapper to issues; also there's a possibility to force sync JIRA with BitBucket to import any missing mappings. All imported JIRA cases have JIRA IDs and old (FogBugz) ID's. So if JIRA would be able to map by external ID, or if changesets contained also JIRA IDs, changeset mapping could be migrated. Any ideas?
I don't believe there is a way to map changesets to issues during the migratation. However, as a post effort, you might want to explore the changesets resources we support. I have included a link that charts the various commands that can be leveraged. Each section contains a code sample that you can expand and use:
I hope this helps ; sorry I could not be of more service.
Jason | Atlassian
As a project manager, I have discovered that different developers want to bring their previous branching method with them when they join the team. Some developers are used to performing individual wo...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs