we are currently trying to migrate from Trac to Jira, but have one really big problem:
When I use the Trac Importer, the old Trac Issue ID will not be used as the new Jira Issue ID (e.g. Trac-ID is #45623 then it should be TF-45623 in Jira). This is a major problem for us. I know that the old ID is written in an extra field "External Issue ID", but I don't get why this is needed. We gave our customers these IDs and this way it's just chaos...
Is there any way to do this? We can't even just use the CSV import, because we can't get the attachments of an issue imported.
Jira uses a different scheme for identifying issues, and the Trac numbers do not work for it.
The only way you will get the numbers to work the same is if you pad the import, such that your Trac system really does have 1, 2, 3, 4, .... 45623
Thanks for your answer.
Well, as I see it the different scheme is, that Jira puts a projectcode followed by a "-" in front of the ID. I can't see the problem in just using the same ID and putting the code in front of it ;)
But ok, seems like we have just 29 missing numbers, so I can create dummy tickets which I just delete afterwards.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
EaglePicher Technologies is a leading manufacturer of battery systems for diverse industries like defense, aviation, space or medical. As they operate in highly regulated industries, keeping a clear ...
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