Migrating a project from one JIRA to another with scheduled tasks.

Issue #86 closed
Andrey Korolev created an issue

Hello,

There is a task of mirgating projects from one JIRA to another with scheduled tasks. The migration of a project itself has no problems using the Project import functionality because I created all JIRA objects from the source JIRA in the target instance. However I got errors when I tried to Import Scheduled Issues. This happened because of differences in IDs of the objects in the source and destination JIRAs. When I changed a project ID and issue type in exported XML to values from the target system, export succeded. <projectId>12609</projectId> <issueTypeId>10102</issueTypeId>

I wonder if it is enought. There are many other project IDs and issue types in exported XML: - <ParamElement> <paramName>issuetype</paramName> <paramValue>9</paramValue> </ParamElement> - <ParamElement> <paramName>pid</paramName> <paramValue>10401</paramValue> </ParamElement>

Should I change them all before the import?

And there are empty custom fields in XML: - <ParamElement> <paramName>customfield_10102</paramName> <paramValue /> </ParamElement> - <ParamElement> <paramName>customfield_10103</paramName> <paramValue /> </ParamElement> - <ParamElement> <paramName>customfield_10104</paramName> <paramValue /> </ParamElement> which are pobably do not match the target system. Is it safe to leave them untouched or it is better to delete these records from XML?

I wonder if there is any HOWTO to do this task?

Kind regards, Andrey.

Comments (4)

  1. jost

    Dear Andrey,

    Unfortunately You cannot remove param "issuetype", this parameter is required. Please try to set there the same value as in "issueTypeId" paramelement.

    The pid is not important, you can skipout this element.

    Lack of custom fields should not have impact on create Scheduled Issue and it will be created even when those field are required to create issue. But in case of lack required field The scheduled job will won't work and you will have to edit SI and add the corresponding values to restore correct operation of the plugin.

    Kind regards, Jacek.

  2. Log in to comment