Dear all,

I would like to inform you that this issue in the project JPOSERVER is being migrated to the new project JSWSERVER. Your votes and comments will remain unchanged.
Our team at Atlassian will continue to monitor this issue for further updates, so please feel free to share your thoughts or feedback in the comments.

Sincerely,
Aakrity Tibrewal
Jira DC

As we onboard larger organizations we must be able to have cross portfolio dependancies in JA.  

Hi Roi,

Good to see the dependencies outside the plan in the Portfolio 3.0! This really helps with stakeholder engagements.

What a must have feature is for us, is the ability to let a outside dependency influence the planning of our roadmap. We plan our issues and our dependencies in collaboration with the other involved teams.

I envision two scenarios (static / dynamic) how we could use portfolio to manage outside dependencies:

Static scenario

I assume there is an understanding between the involved teams on when the depending issue will be started and completed. In this scenario I would like to be able to set (agreed) start and end times in my portfolio on the outside dependency so that this will influence the planning of my own issues.

Dyanmic scenario

In the dynamic scenario I assume that both sets of teams use portfolio for the development of their own products. I would like to use the start and end times of the outside dependency as it is planned in the outside portfolio. If the outside portfolio is updated this would dynamically be reflected in my own portfolio.

Keep up the good work, we really appreciate it.

Hope to hear from you soon!

Hi Roi,

We were very happy to see the cross plan dependencies showing up in the Portfolio 3.0 UI!  This definitely satisfies our "must have" requirement.  As a next step, we are optimistic that a Portfolio 2.0-like Dependency Report will be available soon in the 3.0 experience so users don't have to switch between the reports.  Other reporting like Capacity and Themes would be great if they were also accessible via the 3.0 experience.

Thanks!  We are looking forward to future improvements, please keep up the great work!

Hi all, my name is Roi and I'm a Portfolio for Jira product manager. About a month ago, we shipped Portfolio 3.0.

Among the new features, there is also the ability to view issue dependencies outside of the plan when clicking on a dependency icon. 

While it's not a complete solution, I'd like to learn more on the pain points involved and whether this solution solves some of them.

I attached an image of the solution to the issue (point #5). Please comment below your feedback.

Adding my voice to this issue.  I represent a potential customer of "Portfolio for Jira" and I will say simply displaying and taking into account dependencies on issues outside of the plan is a "must have" for our team.  I foresee us having to have larger, all-encompassing "Plans" to allow for all potential dependencies to be within the scope of the plan.  However, this may mean that multiple PMs on different projects will have to be working within the same "Plan" which is not ideal.

Please, please, please consider this for Portfolio 3.0 <3

This should include easily pulling in dependent efforts into the plan scope.  It would be nice to have it as an option in the set up, to include or exclude work dependent on plan scope and include or exclude work that the plan depends on (Depends on plan or Plan depends on.)    There are other related requests for better visuals in gantt views but this is specifically to make it easy to pull into the plan scope.