Uploaded image for project: 'Jira Cloud'
  1. Jira Cloud
  2. JSWCLOUD-19388

Identify Out-of-Plan Dependencies

XMLWordPrintable

    • 2
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      NOTE: This suggestion is for JIRA Portfolio Cloud. Using JIRA Portfolio Server? 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.

      Additionally, it would be desired to list external issues that block external issues that are dependent on issues within the plan's scope. For example, an external issue blocks another external issue which blocks the Epic within the plan's scope. As of now, we can only go as far as being able to see the external issues that block issues within the planned scope, although not the external issues that block another external issue on which an issue within the plan's scope is dependent.

              Unassigned Unassigned
              a9373970cdd2 Haddon Fisher
              Votes:
              5 Vote for this issue
              Watchers:
              9 Start watching this issue

                Created:
                Updated:
                Resolved: