Mapping changesets to issues, migration from FogBugz+Kiln

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?

1 answer

0 votes
Jason Worley Atlassian Team Apr 26, 2013


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.

Happy Coding!

Jason | Atlassian

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 06, 2018 in Bitbucket

Upgrade Best Practices

Hello! My name is Mark Askew and I am a Premier Support Engineer for products Bitbucket Server/Data Center, Fisheye & Crucible. Today, I want to bring the discussion that Jennifer, Matt, and ...

1,906 views 7 10
Read article

Atlassian User Groups

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!

Find my local user group

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

Groups near you