Importing Bitbucket Issues Into JIRA OnDemand: How to preserve key ordering?

Question

I'm doing an evaluation of JIRA OnDemand at the moment.

I've imported the list of issues from the issue tracker of one of my Bitbucket repositories, and it mostly seems to have worked.

The one strange outcome I've noticed so far is that the ordering of the new issue keys doesn't track with the ordering of the issue numbers from the Bitbucket issue tracker.

That is, Bitbucket's #2 is now XYZ-3 in JIRA, #3 is XYZ-8, #4 is XYZ-7, and so on in random fashion.

The Bitbucket issue numbers came over correctly in the "External Issue ID" field, but is there a way to cause them to be the numbers of the corresponding issue key?

I'm more than a little surprised that this isn't the default behavior.

aMarcus · Answer

I can't find any evidence that the plugin should or should not do this. To be sure, I opened https://ecosystem.atlassian.net/browse/JIM-1079 to track a response from the developer. You can vote on and monitor that ticket by signing up a free account.

Repo Master · Answer

@Jason, I think you missed the point of my question. I know the two trackers work independently, yet JIRA does support import of issues from the Bitbucket tracker (which is essential for making a switch to JIRA and still be able to track existing issues). My question is about how to get that import functionality to preserve the original issue numbers, rather than just randomly renumbering the imported issues.

AgentSmith · Answer

The Bitbucket and JIRA issue trackers are mutually exclusive. From our documentation:

If you find the Bitbucket issue tracker lacks the features you need, you can choose to use JIRA together with the JIRA DVCS Connector or you can use another issue tracker available through Bitbucket services.

https://confluence.atlassian.com/display/BITBUCKET/Use+the+issue+tracker

That being said, if you wanted to leverage the JIRA issue tracker, this info will guide you through the process:

https://confluence.atlassian.com/display/AOD/Processing+JIRA+issues+with+commit+messages

Hope this helps!