Merge one JIRA Instance with another with all configuration

[Sachin Dhamale]

I have two JIRA instance JIRA A and JIRA B. Now i want to merge JIRA A with JIRA B with all configuration like workflow, screen, schema etc. Is it possible with programmatically by creating plugin?  means does all API available for this. or any other way to do this

Awaiting for reply.

Thanks in advance

[Petar Petrov (Appfire)]

Hi Sachin,

Merging two instances of JIRA is a pretty complex task. We at Botron have developed a product which will help you in that process and solve the most complex problems - Configuration Manager for JIRA. Using our tool you can take a snapshot of the configuration of JIRA A and merge it into JIRA B. If you want to know more or see a demo, drop us an email at support@botronsoft.com. 

[Sachin Dhamale]

Hi Peter,

Thanks for reply. i will look into this plugin if i have any queries i will drop you mail.

[Nic Brough -Adaptavist-]

Yes, it's possible, but you'll find it can get very complex, very quickly.

I'd strongly recommend a look at Botron's "Configuration manager" add-on.  This allows you to take a project (or system) config (fields, workflows, screens etc) from one system and import it into another. 

Once that has been done, then you can use JIRA's built-in export xml (of everything) to get a file which you can point the "project import from xml" function at.

[Sachin Dhamale]

Hi Nic,

Thanks for reply. I will explore mentioned plugin for configuration but "Project import" is not a feasible option for me because i have lots of project to merge and it will take more time.

[Nic Brough -Adaptavist-]

There's two parts to merging from one JIRA to another.  The configuration and the issues.

Botron's Configuration Manager will do the horribly complex part for you - the configuration (I once gave an estimate of 4 weeks for merging a configuration set manually that CM can do in a couple of hours).

The issues are very simple if you use project import.  But, you have to have the configuration in place so you can import the issues into the pre-configured setup.

If you don't want to use "project import", then you're in a world of pain - you're going to need to do the issues with a CSV import, plus lots of changes afterwards, or botching vast amounts of SQL (and deperately hoping you get every single item correct), merging huge swathes of XML, or writing scripts and/or add-ons to do everything that project import already does.

[Sachin Dhamale]

right, thanks for suggestion nic.