• 3
    • 8
    • 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.

      Atlassian Update - 23 April 2015

      Hi everyone,

      Thanks for voting and commenting on this issue. Your input in the comments helps us understand how this affects you and what you're hoping to accomplish with JIRA.

      At this time, this suggestion is not on the JIRA development roadmap. Please remember that jira.atlassian.com is one of many inputs for the JIRA roadmap. You can learn more about our process here.

      I understand that our decision may be disappointing. Please don't hesitate to contact me if you have any questions.

      Regards,
      Dave Meyer
      dmeyer@atlassian.com
      Product Manager, JIRA Platform

      It seems that there is no way (or none that I'm aware of) how to search for issues that are blocked by unresolved issues, resolved issues or not blocked by other unresolved issues at all (to see which issues I can work on). That would be really useful feature, because now I can have saved search filter with issues assigned to me, but I have to go through them one by one to see which are not blocked by any other. Also, it's useful to see which issues are blocking others, because we usually want them to be done first.
      I found a "linkedissues" function but that can refer to only one issue.

            [JRASERVER-22024] Ability to search for blocked / blocking issues

            Raj Vora added a comment - - edited

            Hi! I have a query that checks unblocked tickets; I use a similar JQL statement to the one posted previously:

            issueFunction in linkedIssuesOf("resolution != Unresolved", "blocks") and resolution = Unresolved

            One of my tickets has multiple blockers and when just one of its blockers gets resolved (the other one is unresolved), the parent ticket appears on this query which it obviously shouldn't because its still blocked. Has anyone else experienced this same issue?

            I have posted this question here too (if people feel its easier to discuss in another location):

            https://community.atlassian.com/t5/Jira-discussions/Unblocked-ticket-query-fails-with-ticket-containing-multiple/m-p/1356620#M10966

            Raj Vora added a comment - - edited Hi! I have a query that checks unblocked tickets; I use a similar JQL statement to the one posted previously: issueFunction in linkedIssuesOf("resolution != Unresolved", "blocks") and resolution = Unresolved One of my tickets has multiple blockers and when just one of its blockers gets resolved (the other one is unresolved), the parent ticket appears on this query which it obviously shouldn't because its still blocked. Has anyone else experienced this same issue? I have posted this question here too (if people feel its easier to discuss in another location): https://community.atlassian.com/t5/Jira-discussions/Unblocked-ticket-query-fails-with-ticket-containing-multiple/m-p/1356620#M10966

            Gavin - have you ever been able to figure this out? I'm very interested to know - claudia.dineen@dxc.com Thank you!

            Claudia Dineen added a comment - Gavin - have you ever been able to figure this out? I'm very interested to know - claudia.dineen@dxc.com Thank you!

            Marc Moroz added a comment -

            James, you can do it with Adaptavist Scriptrunner but you can't do it without an add on and that's a pretty basic expectation for a ticketing system.

            We have Scriptrunner and even with a paid add on, you don't enough.  Sure you can find what's blocked by or blocking a specific ticket, but you really can't report on it.  For example, if you want to get a list of issues that are blocked, and also list what's blocking them (because that's the obvious next question, all you can really get is the Key of the blocking issue.  Unless everyone using Jira has all of the keys memorized, you're going to need to at least see the Summary.  I'll clarify.

             

            Issue Key: ABC-123

            Summary: Write Code

            is blocked by

            Issue Key: ZZ-99

            Summary: Build Environment

             

            You can link these two to show that ZZZ-99 is blocking ABC-123

            You can search for blocked issues (ZZZ-99 included) with something like this:

            • issueFunction in hasLinks("is blocked by")

             

            There is no field/column specific to blockers.  The closest you'll get is Linked Issues which has 2 problems:

            1. It only returns the key
            2. The column shows ALL linked issues regardless of why their blocked

             

            So you get something like this back:

            Key | Summary | Linked Issues

            ABC-123 | Write Code | ZZ-99, FOO-444, etc.

             

            You could reverse the search to look for blocking instead of blocked issues but you'll have the same problem with trying to see what's blocked.

             

            I don't think most people are going to look for blocked/blocking information on an issue by issue basis.  Most of us run a query looking for a list of results, usually across several projects, and need the information to be easily accessible.  Instead, you have to click in to each issue and try to find the real information and then manually make a report out of that if you want to send information on.

            Marc Moroz added a comment - James, you can do it with Adaptavist Scriptrunner but you can't do it without an add on and that's a pretty basic expectation for a ticketing system. We have Scriptrunner and even with a paid add on, you don't enough.  Sure you can find what's blocked by or blocking a specific ticket, but you really can't report on it.  For example, if you want to get a list of issues that are blocked, and also list what's blocking them (because that's the obvious next question, all you can really get is the Key of the blocking issue.  Unless everyone using Jira has all of the keys memorized, you're going to need to at least see the Summary.  I'll clarify.   Issue Key: ABC-123 Summary: Write Code is blocked by Issue Key: ZZ-99 Summary: Build Environment   You can link these two to show that ZZZ-99 is blocking ABC-123 You can search for blocked issues (ZZZ-99 included) with something like this: issueFunction in hasLinks("is blocked by")   There is no field/column specific to blockers.  The closest you'll get is Linked Issues which has 2 problems: It only returns the key The column shows ALL linked issues regardless of why their blocked   So you get something like this back: Key | Summary | Linked Issues ABC-123 | Write Code | ZZ-99, FOO-444, etc.   You could reverse the search to look for blocking instead of blocked issues but you'll have the same problem with trying to see what's blocked.   I don't think most people are going to look for blocked/blocking information on an issue by issue basis.  Most of us run a query looking for a list of results, usually across several projects, and need the information to be easily accessible.  Instead, you have to click in to each issue and try to find the real information and then manually make a report out of that if you want to send information on.

            +1

            JamieA added a comment - - edited

            To clarify the comment above, that requires ScriptRunner for JIRA, documentation for issue links functions is here.

            JamieA added a comment - - edited To clarify the comment above, that requires ScriptRunner for JIRA , documentation for issue links functions is here .

            You can do this with JQL:

            issueFunction in linkedIssuesOf("resolution is empty", "blocks") and resolution is empty
            

            See Linked Functions for a bit more information.

            James Crosswell added a comment - You can do this with JQL: issueFunction in linkedIssuesOf( "resolution is empty" , "blocks" ) and resolution is empty See Linked Functions  for a bit more information.

            sparr added a comment -

            +1
            I need to be able to filter blocked issues out of my default kanban board view, so I'm only looking at tickets I can work on.

            sparr added a comment - +1 I need to be able to filter blocked issues out of my default kanban board view, so I'm only looking at tickets I can work on.

            Dan Moore added a comment -

            So bizarre that we can't ask Jira "Which tickets are blocking other tickets?".  That's probably the most useful thing one could ask a ticketing system.

            Dan Moore added a comment - So bizarre that we can't ask Jira "Which tickets are blocking other tickets?".  That's probably the most useful thing one could ask a ticketing system.

            Marc Moroz added a comment -

            Very surprised this doesn't exist.  This is a missing core feature.

            Marc Moroz added a comment - Very surprised this doesn't exist.  This is a missing core feature.

            j.jarvela added a comment -

            This is a basic functionality any JIRA customer, who has more than one project running in Jira. 

            It's not a rocket science to get this as standand feature in Jira- please get this done.

            j.jarvela added a comment - This is a basic functionality any JIRA customer, who has more than one project running in Jira.  It's not a rocket science to get this as standand feature in Jira- please get this done.

              Unassigned Unassigned
              zdenek.zikan Zdeněk Zikán
              Votes:
              236 Vote for this issue
              Watchers:
              120 Start watching this issue

                Created:
                Updated: