How do I make existing changesets work after importing data from Trac to Jira?

[Pradeep Pamidipalli]

I have successfully imported all the tickets from Trac to Jira. We have subversion changesets tracking to all the tickets in Trac.

What can I do to make the existing changesets work as a link to point to subversion changes after importing data to Jira.

Thanks,

Pradeep

[Remi Leblond]

Here's a solution if you want your commit messages to be linked to your JIRA issues (and if you want your JIRA issues to be linked to your commits in bitbucket)

Before pushing your local git repository (coming from your SVN) to bitbucket, run this command:

git filter-branch -f --msg-filter "sed 's/#/XXX-/'" --tag-name-filter cat -- --all

Where XXX is the key of your project.

This will replace all references to a Trac ticket (i.e. See #522) to it's equivalent JIRA issue (XXX-522), provided that you imported the Trac issues into Jira.

All the commits will be linked both ways, just like magic.

[JolyonKB]

I wrote a PHP script to rewrite the link tags in the trac.db before we imported. Here's a link to the script with user story and references for anyone else who runs into this one:

How I imported a 4 year old legacy trac with multiple subversion repositories and commit hooks to Atlassian JIRA