nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

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

NS_53t6s6

...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.

Comments

Matthias Gaiser _K15t_

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.

Cheers,
Matthias.

NS_53t6s6

Thank you, Matthias.

francis

(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

Downstream issues (such as customer complaints, feature requests, opportunities) get raised in the master JIRA
Based on specific criteria (product, type of issue, source ...) exalate will automatically delegate the issue to the right team JIRA
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

Francis

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

advanced-roadmaps

epic

scaled-agile

safe