Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-14747

Ability to search for issues with blockers linked to them

XMLWordPrintable

    • 1
    • Hide
      Atlassian Update – 21 December 2018

      Dear Jira users,

      We’re glad to announce that this issue will be addressed in our upcoming 8.0 release.

      You can find more details about our 8.0 beta release here — https://community.developer.atlassian.com/t/beta-for-jira-8-0-is-up-for-grabs/25588

      Looking forward to your feedback!

      Kind regards,
      Syed Masood
      Product Manager, Jira Server and Data Center

      Show
      Atlassian Update – 21 December 2018 Dear Jira users, We’re glad to announce that this issue will be addressed in our upcoming 8.0 release. You can find more details about our 8.0 beta release here — https://community.developer.atlassian.com/t/beta-for-jira-8-0-is-up-for-grabs/25588 Looking forward to your feedback! Kind regards, Syed Masood Product Manager, Jira Server and Data Center
    • 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.

      NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.

      A search I would find handy is to be able to pull up all issues that are linked to another as a 'blocker'
      (and in a seperate search, those that are 'blocked')

      so we can see what issues are stopping others progressing

      apologies if this is already possible, but I can't see it in the version of 3.11 enterprise I'm using (was set up before I started work here, and I have no admin rights )

              agniadzik Artur Gniadzik
              8bd10cb4dd18 Rachael Russell
              Votes:
              48 Vote for this issue
              Watchers:
              22 Start watching this issue

                Created:
                Updated:
                Resolved: