We are in the process of migrating our issue tracker from FogBugz into Jira OnDemand and our source code from Kiln into Bitbucket.
The problem we have found is that we are going to lose our historical links of our issues and code commits. We can easily use Jira and BitBucket going forward with smart commits, however we would really like to be able to link our source code to our imported issues.
The new Jira issues are linked via the External Issue ID to the FogBugz issues, so there is a link that a human can go through to find the code, however it's not the best and we would prefer to have the issue and commits geniuenly linked together.
I have hunted around for information on this, but so far I have found nothing that seems to provide an answer.
Any help is seriously appreciated.
At this time, the DVCS Connector can only recognize JIRA Issue keys in commits from a repository. You may want https://jira.atlassian.com/browse/DCON-256to be completed in the future. Otherwise, you can open a new ticket there to request that this feature be added.
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
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