Connecting Locally hosted Jira to another Locally hosted Jira Edited

[Andrew Tud]

Hi, All,

We have the following use case:

Our company is using 2 locally installed Jira instances hosted in our private network and we would want to link these 2 Jira instances together. The first Jira is used as a ticketing system for System Engineers and Software Engineers while the second Jira will now be used for Software Development Project for only Software Engineers which will use Scrum Methodology. As you can see, the two Jiras are different in their use cases and since the developer Jira will now be used to plan sprints and prioritized backlogs, it is very crucial for the Product Owner to be able to know all developer tickets from the other ticketing Jira in one Backlog to help prioritize and plan sprints for exact duration in the developer Jira. With this use case, I would like to ask the following:

1. Is it possible to link the two Jiras (ticketing Jira and development Jira) so that when a support admin creates a request to the ticketing Jira that will be assigned to a developer the ticket/issue will also be created as a duplicate and linked issue in the Backlog of the development Jira?

2. The development Jira will have a different workflow (Scrum based) than the ticketing Jira (ticketing based). Would it be possible to map the workflow of the development Jira to the ticketing Jira so that when a developer moves an issue to the done column (for example) the issue status in the ticketing Jira will transition to resolved (for example). 

Thank you very much.

[Nic Brough]

You'll either need to write a service that can update both Jira systems externally, or use add-ons that enable them to talk to each other in more detail than just a simple "link to another system"

I'd take a look at Backbone and Exalate.  Your requirement is pretty much the specification for what they both do.