Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Can Portfolio for Jira be used across different Jira-instances?

...e.g. to merge and sync data from several Scrum/Kanban sprint&product backlogs in one of the already existing project.

- Is it included is the basic functionality of Portfolio for Jira?

- Can it be achieved through installation of additional plug-in (which one exactly)?

We are looking for a solution, which will allow to track the progress on a program level, create common roadmap etc. Migration to one single instance is not possible at the moment.

Thank you in advance for any ideas.

2 answers

2 votes
Marketplace Partner
Marketplace Partners provide apps and integrations available on the Atlassian Marketplace that extend the power of Atlassian products.
Mar 13, 2019 • edited

(I'm with the team of Exalate)


We have once setup a configuration which we call a star network

The star network is an exalate configuration where one central master JIRA is used to raise program level issues which then fan out towards the different slave JIRA's which are used to handle product/component level issues.


The general flow is

  1. Downstream issues (such as customer complaints, feature requests, opportunities) get raised in the master JIRA
  2. Based on specific criteria (product, type of issue, source ...) exalate will automatically delegate the issue to the right team JIRA
  3. Progress on the team level JIRA's are reported back to the master JIRA where an overall status can be generated or inserted into a portfolio plan


start diagram



There are a couple of caveats whenever setting up such configurations, such as ensuring there is some consistency between the workflows.  This can be handled in different ways.


If you would like to know more - just feel free to book a meeting here




0 votes
Matthias Gaiser _K15t_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Mar 11, 2019

Hi @NS

welcome to the community.

Portfolio for Jira cannot be used across different Jira instances, but you can synchronize your issues from different Jiras into one. On this one instance, you can then either simply create your own boards or dashboard gadgets if that is enough for you - or use Portfolio if you like.

There are multiple solutions for issue synchronization out there. I'm part of the team behind Backbone Issue Sync, therefore I'm probably biased in recommending a solution. But most of the solutions should be able to solve your needs.


Thank you, Matthias. 

Like Matthias Gaiser _K15t_ likes this

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events