My use case is the following
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?
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.
There are different solutions on the marketplace - check following query
We are the team behind Exalate (which is one of these solutions)
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
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
As part of the Bitbucket product team I'm always interested in better understanding what kind of impact the use of our tools have on the way you work. In a recent study we conducted of software devel...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs