nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Refrences lost after Trac to JIRA migration

Taj Pelc

We are trying to migrate to JIRA from Trac and plan on using it in combination with GreenHopper for scrum. We are using the built in Trac import plugin.

In Trac we have requirements which are equivalent to epics in JIRA and reference multiple stories that need to be carried out in a sprint.

In the new setup we would use epics to group stories together and add sub-tasks to stories.

When importing from trac, the issue types are remaped as such:

requirement => epic
story => story
task => task
bug => bug

After the import the references between Trac items are not recreated in JIRA.

Is there a way to preserve refrences or alternatively a script or a tool to automate the creation of refrences. Manually creating them is not an option, because there are over 5000 issues and we would like to keep all of them to save history.

Accepted answers

Taj Pelc

You have to do some scripting in order to rewire everything after the import if you want to retain the same structure. This is the flow that I followed:

Import the trac project with the built in jira importer and remap the fields as desired (Epics, Stories, Tasks, Bugs)
Get a list of all the issues from jira and trac and build a map (jira_id => trac_id), jira stores the old id in a custom field named "external issue id"
Build a mapping of issue links from agilo database table "agilo_link" in trac
Use the REST API to add stories to epics (/rest/greenhopper/1.0/epics/$EPIC_ID/add)
Use the REST API to rename epics (/rest/greenhopper/1.0/xboard/issue/update-field.json)
Use selenium to convert tasks to sub-tasks with stories for parent issues

Check with the documentation for a detail how to of the REST API. The steps should be fairly easy if you have a programming background.

All comments

Immanuel Siagian

Hi Taj,

Would you mind provide us the Trac Version? I will try to import from Trac and see whether this behaviour is replicable. Thanks

Taj Pelc

I think I know where the problem is. The references are kept by an addon for trac, Agilo for Trac 0.9.8 with Trac Version 1 in a table agilo_link. I believe I will have to replicate the references manually with a CLI script after the import.

Immanuel Siagian

Thanks for this piece of information Taj. To be quite honest, I am not familiar the Agilo Trac Plugin, but do let us know if there's anything we can do to assist you.

Cheers.

Immanuel Siagian

Thanks for this piece of information Taj. To be quite honest, I am not familiar the Agilo Trac Plugin, but do let us know if there's anything we can do to assist you.

Cheers.

Iván Párraga2

Hi Taj,

I'm experiencing the same problem as I need to import a Trac installation with Agilo plugin. Did you manage to import these reference fields?

Cheers,

Iván

Taj Pelc

This is a question, not an answer . Check below for my solution.

Taj Pelc

You have to do some scripting in order to rewire everything after the import if you want to retain the same structure. This is the flow that I followed:

Import the trac project with the built in jira importer and remap the fields as desired (Epics, Stories, Tasks, Bugs)
Get a list of all the issues from jira and trac and build a map (jira_id => trac_id), jira stores the old id in a custom field named "external issue id"
Build a mapping of issue links from agilo database table "agilo_link" in trac
Use the REST API to add stories to epics (/rest/greenhopper/1.0/epics/$EPIC_ID/add)
Use the REST API to rename epics (/rest/greenhopper/1.0/xboard/issue/update-field.json)
Use selenium to convert tasks to sub-tasks with stories for parent issues

Check with the documentation for a detail how to of the REST API. The steps should be fairly easy if you have a programming background.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

issue

jira

import

link

trac