Two Jira Instances - Together but Separate?

[lukec]

I have two separate Jira instances on Jira server, 

I'd like Jira instance 1 to be the 'production' Jira and Jira instance 2 to be a 'test' Jira. 

Is there a way to link them such that Jira 1 updates Jira 2 (with prpject / issue data etc), but when I make changes in Jira 2, it does not impact Jira 1?

[Nic Brough -Adaptavist- · Accepted solution]

Not directly.  Jira 2 would break as soon as anyone started to add data to it, rapidly leading to a corrupted database and a Jira that just falls over.

Closest you might get is to set up a one-way "synchronise" using Backbone, Exalate or Watchtower - they can push data out of 1 and into 2 without breaking anything, but it won't be like-for-like.

Simple example 

• User in Jira 1 adds an issue   (Call it ABC-x)
• Sync pushes it over to Jira 2 (Assuming Jira 2 has not been touched since it was cloned from Jira 1, ABC-x is created)
• User in Jira 2 adds and issue (ABC x+1)
• User in Jira 1 adds an issue (ABC x+1)
• Sync pushes it over to Jira 2 (ABC x+2)

[lukec]

Thanks Nic

[Joe Pitt · Accepted solution]

Like @Nic Brough -Adaptavist- said you can't touch #2 which I don't believe is what you really want. I have a production and test version but only use the test for trying out new plugin, testing a JIRA upgrade or something else that may break production. If I want a new workflow screen, issue type, etc. I build it in production and apply it to a project only I can see. I can then give selected users access to see if they like it. If we decide to implement it everything is already in the production instance so it's easy to use the parts in a production project.