We are thinking of migrating to JIRA from Trac. Our code repositories are hosted at GitHub. I've done a test import of the trac and then went to set up the link to GitHub. Nothing shows up in the commit tab.
Of course, since we've been using Trac commit messages have been referencing issues in the way Trac expects - i.e. Re #1234 or refs #1234. Is there a way to get the existing commits to appear under the commits tab (the issue numbers do match after the import)? I realise that in general there'd be an ambiguity, but we only have one project in our JIRA account. (Of course if we went with JIRA we would start including the correct key in the commits, but we would really like to have the historical commits fully included as well.)
Did you establish the link via the DVCS connection? You can verify that by going here:
More details are available here:
As far as syntax, it would be ISSUE_KEY #<transition> <comment_string> so for example:
JRA-090 #close Fixed this today
Full list of syntax options:
Hope this helps!
Yes, the link is set up and I can make test commits appear fine. What I want to know is whether it's possible to make our 29k existing commits show up under the commits tab for the 8000 issues imported from trac. Naturally, the commit messages for these do not use ISSUE-KEY, but rather "Re #NNNN".
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Hey Atlassian Community! Today we are launching a bunch of customer stories about the amazing work teams, like Dropbox and Twilio, are doing with Jira. You can check out the stories here. The thi...
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
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs