Associating Commits from older Tracking System to JIRA

[Brian Lancaster]

We have been using CollabNet's TeamForge for all our project tracking and are moving to JIRA.

Along this time we have been using the style for association of commits to artifacts that looks like this. A given artifact would have a number 1234 and the index would be 'artf1234'. This index would be included with all commit messages and would be associated with the artifact within TeamForge.

My repository has thousands of revisions with the old artf1234 references. I want to know a way of getting these existing revisions associated with the imported versions of the artifacts within JIRA. All my imported artifacts are now issues with the project key 'NCF'.

It would seem that I could create a custom field and place the old 'artf1234' number in there and have the system search for these numbers and associate with the given commit. All the while using the new indexing style with NCF-1234 on a go forward basis.

For the record I am using JIRA 5.0.1 and FishEye 2.7.11.

Thanks!

[tao sun]

Hi,

We use Teamforge for our bug tracking and project management, and we'd like to move into JIRA. Could both of you light me up on how to import the existing data from Postgres of Teamforge to JIRA?

Thank you in advance.

Tao

[Dennis Kromhout van der Meer]

I'm not aware of any solution, as this is very specific to your environment and I haven't come across any (internal) documentation that would help you.

If no one else answers this question, I'm more than happy to find the best 3rd party expert to help you create a solution based on your requirements.