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
I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...
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