issue id changed after migrating issues from server to server

[Madhura A S]

Hi,

We are in the process of archiving some of the project which has idalko table grid fields. We have migrated the issues using configuration manager for Jira but idalko table grid fields are not migrated with this plugin.

So we have migrated the idalko table grid fields table by CSV export and import method. These table grid fields are linked to issues using issue 'ID' but issue 'ID' is changed after we migrated issues.

Is there any way to link these fields data to issues? or any other better migration method?. 

Please suggest

Regards,

Madhura

[Nic Brough -Adaptavist- · Accepted solution]

The ID of an issue has to change when you move it to a new project, but that isn't actually a problem here.

You'll need to talk to Idalko about export and import of the table grid data in your fields.

[Madhura A S]

Hi @Nic Brough -Adaptavist- 

Thanks for the response.

We did spoke to the vendor and they suggested to use script runner and JAVA API(https://docs.idalko.com/tgng/display/TGED/Java+API%3A+Groovy+script+examples).

But this is not going to work for us as we don't have the script runner.

Tried to read the issuenum and project from jiraissue table to find the new 'id' in target server but  there is a difference between rows in table grid customfield data and the actual issues that have table grid field. May be issues are deleted or moved but table grid field table still retains data for issues.

I'm confused here.

[Nic Brough -Adaptavist-]

If you have migrated the issues, but not the table-grid data, you are going to have to go through a manual mapping exercise - extract the data from the old data, work out what issue key it is in the new one, and then import (I've not tried to export/import table-grid data recently, I don't know how to import - if you can format the new issue id + table grid data into a "one line of CSV per issue" format, an import might do it.  But you'll need to do that mapping exercise.