Page tree
Skip to end of metadata
Go to start of metadata

The problem - when exporting/importing insight into another Jira it gets new ids and keys.

This makes the issues lose the connection to the insight schema when migrating issues from one Jira to another.


  1. Tag objects with the issue key, to be able to recreate the link after.
  2. Import the insight schema
  3. Import the issues
  4. Re-link the issues to insight objects



Tag objects with the issue key, to be able to recreate the link after.

On the image above we see the linked issues connected to the user database. To preserve these we need to tag the object with a identifier that will be the same. 

Create an attribute called Migration that will be used to identify the objekt late on.


Add an automation to tag the object with its own key

Results in

Migration has now the original objekt key.


Do step 2 and 3 using export / import of project and object schema


Update the custom fields to map to new objectType Ids.


Step 4. Re-link the issues to insight objects


  1. Go to iHub
  2. Click on Credentials and add basic auth to the other Jira
  3. Click on outbound Integrations
  4. Click New
  5. Select template Jira Core →Search
  6. In the URL add ?jql=project=myP and customfield_x != empty 
  7. This will search the Jira for issues with the custom field that is not empty.
  8. Click New again
  9. Select template Jira Core →Edit Issue
  10. Select Parent to be the action above
  11. Enter the URL to the other Jira that will be fixed with references.
  12. Go down to the body section and specify the custom field that will be update
    {
        "fields":{"customfield_10201":"{{key}}"}
    }






  • No labels