NOTE: This suggestion is for JIRA Portfolio Server. Using JIRA Portfolio Cloud? See the corresponding suggestion.
As a plan owner, I would like to know about any stories within the scope of my plan which is marked as blocked by an issue outside of my plan because those blockers need to be resolved before my plan is accurate.
We have one project per team, and are further organized around either platform or application. Our application teams has milestones and releases and would like to use JIRA Portfolio to plan and manage them. However, many of their features are dependent on the development or fixing of underlying platform work, which would not appear on their plan.
It would be nice if Portfolio could do some scheduling or other logic around these "external" dependencies, but at the very least I need a report or list of the stories outside of my plan which are blocking stories within so that I can run them down, get timing, etc.
- is duplicated by
-
JSWSERVER-24915 Determine dependencies across different plans
- Gathering Interest
- relates to
-
JPOSERVER-1822 Better support for managing external dependencies
- Closed
-
JPOSERVER-1825 support on external dependency
- Closed
-
JSWCLOUD-19388 Identify Out-of-Plan Dependencies
- Closed