Jira bulk issue update from one server to other

[Atul Patil]

I am planning to bulk update and create the issue from 1 jira server to another. The source is 7.2.3 version and destination is 7.13.1 version. What is the best possible way to do that, the Jira rest API causing lots of issues, limiting only a few fields to edit. Any response is greatly appreciated

Thank You  

[Earl McCutcheon]

Hello Atul,

Migrating or Syncing data between two instances using the API is not an effective approach as Items such as the created date cannot be set using the API's.  As en example on this, when you have issues in the source instance created in the past and then synchronize today, the created date on the target instance for that issue will be today not the historical value from the source instance.

If you are planning on keeping the data on two independent instances check out our guide on "Federating Jira - managing multiple instances" the recommendation is going to be keeping projects separated out on each instance independently for organizational needs and will still require running migrations to get issue data transferred to the other site, and use Remote issue linking  to connect issues on the alternate site for visibility to users that have access to each location.

To preserve the issue history and if your planning on doing a single migration then the approach you would want to take is a Project Migration, and there are tools that can be used to make the migration easier as covered in "Migrating projects to another Jira instance"

If you are planning on doing this on a regular basis you would want to look into a tool like "Issue SYNC - Synchronization for Jira" or possibly using "Configuration Manager for Jira" as discussed in this previous post:

• https://community.atlassian.com/t5/Jira-questions/How-to-Move-a-set-of-Issues-between-instances-of-JIRA/qaq-p/699332

Regards,
Earl