Separate instances of JIRA into a unified managed view

[ThomasS]

My use case is the following

• Public / Private JIRA: JIRA offers the functionality to make specific content only accessible to identified groups through permission schemes and user groups. However, many customers, including Atlassian itself, prefer to run internal content (e.g. development) on a separate instance inside the firewall. A dedicated instance is then set up to host external content (e.g. support / public feature requests) and make it accessible to customers and partners.

I do not see a good way to integrate these separate instances of JIRA into a unified managed view. I am looking at JIRA Portfolio but it also looks like it is restricted to one instance of JIRA which would make it scalability attributes less than desired. Does anyone have any ideas?

[Nic Brough -Adaptavist-]

Most people who need to do that actually make their JIRA public, but limit external access to a set of projects.  So you end up with 1 JIRA (with a single Portfolio ), X public projects and Y private ones. 

You usually find it useful to enable issue security in the public ones too, so you can take any issue you want to hide and flip it, rather than having to move it.

[Ignacio Pulgar]

Check Backbone:

https://marketplace.atlassian.com/plugins/com.k15t.backbone.backbone-issue-sync/cloud/overview

[francis]

Hi Thomas,

There are different solutions on the marketplace - check following query
https://marketplace.atlassian.com/search?q=issue+sync

We are the team behind Exalate (which is one of these solutions)  
https://marketplace.atlassian.com/plugins/com.exalate.jiranode/server/overview
It fully covers your use case, and we are very willing to help in case you decide to evaluate our solution.

Feel free to book a meeting at your convenience here
https://exalate-demo.youcanbook.me

Francis