Copy all issue details including comments and attachments to another JIRA Instance

[Danielle Cantrell]

I'm looking for a way to copy all historic detail including comments and attachments from 1 JIRA instance to another.  We do not need the issues to sync.  This is only for back up of the work that has been completed TD.  We would want to do this "import" periodically to address new issues that have closed but it does not need to be automatic.  We would be copying from a cloud instance to a server instance

[Matthias Gaiser _K15t_ · Accepted solution]

Hi @Danielle Cantrell

while you mentioned that you don't need to sync the issues, you could still use an issue sync app for your use case. In its configuration you'd need to make some decisions like:

• Which issues do you want to sync?
  Probably only completed issues.
• How often do you want to sync?
  Since you don't want to really sync, this could be like once a week/month.
• Which fields do you want to sync?
  It sounds like you want to sync all the fields.

One other option, is that you write your own script which uses the Jira Server and Jira Cloud REST API to get the issues from your cloud instance and create them on the server instance.

Note: Both solutions will result in an issue history which will not be the same as your cloud instance. In Backbone Issue Sync, you have the option to sync the issue history to a text field (I'm not sure about the other issue sync apps).

Cheers,
Matthias.

PS: I'm working for the team behind Backbone Issue Sync, one of the issue sync apps.

[Danielle Cantrell]

Thank you Mattias,  1 more question.  Is there a minimal version of a JIRA server instance that needs to used for this sync?

[Matthias Gaiser _K15t_]

You can see the minimum version always on top of the marketplace listing.

Currently, this is Jira 7.0.0 for Backbone Issue Sync.

[Aisen]

@Matthias Gaiser _K15t_ to be able to use Backbone issue Sync for jira should the add-on be installed on both sides? 

[Matthias Gaiser _K15t_]

@Aisen, you need to license every instance which you want to use for the issue synchronization.

In the standard operation model, you would install Backbone in both Jira instances and get an Atlassian Marketplace license for them.

In case you're restricted from installing Backbone in Jira B, you can still use Backbone by installing & licensing it in Jira A. In addition to the Atlassian Marketplace license, you'd need a Remote License as a replacement license for Jira B.

PS: Please note that Jira A needs to be a Jira Server/Data Center for technical reasons.

[Aisen]

@Matthias Gaiser _K15t_  thanks a lot.