Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

issue id changed after migrating issues from server to server


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




1 answer

1 accepted

0 votes
Answer accepted

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.

Hi @Nic Brough _Adaptavist_ 

Thanks for the response.

We did spoke to the vendor and they suggested to use script runner and JAVA API(

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.

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.

Suggest an answer

Log in or Sign up to answer

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you