Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-11906

Visualize dependencies between issues on the agile boards

    XMLWordPrintable

Details

    • Suggestion
    • Resolution: Duplicate
    • None
    • None
    • None
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

    Description

      JIRA allows to express dependencies between issues by adding links (by default, "depends on"/"blocks"). On the agile boards, these dependencies can only be seeen when selecting a specific issue and scrolling to the linked issues section.

      As a developer choosing an issue to work on the Kanban or Scrum boards,
      I would like to have these dependencies visualized on the issue cards
      so that I can make a more informed choice and have a reduced risk of wasting time by choosing a "not yet workable" issue.

      As a product owner ranking issues on the Kanban or Scrum boards,
      I also would like to have the dependencies visualized on the issue cards
      so that I don't inadvertently rank issues the wrong way around.

      The concrete link types to count as "blocking" should ideally be configurable; practically, the standard "depends on" type could also suffice.

      Suggestions for this visualization:

      • arrows drawn between issues with dependencies,
      • icon or a different (darker) card color for issues blocked by other open issues,
      • a list of blocking issue numbers (with links) on the cards.

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              42a5cc0c7740 Fabian Schmied
              Votes:
              1 Vote for this issue
              Watchers:
              8 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: