I have seen examples of Kanban boards where a work item is marked with a red sticker or something similar if it is blocked for some reason. Is there a way to do this in the JIRA Kanban board? Among the things I thought about already: * Setting the issue as a Blocker is not what I want; that would just mean it should be prioritised. * Using a JQL query for an "is Blocked by" link could do the trick, but it would be nice to have something simpler. * There seems to be some plugins available, but my preference is on built in functions.

nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Marking an issue as blocked in JIRA (Kanban)

Eirik Midttun

I have seen examples of Kanban boards where a work item is marked with a red sticker or something similar if it is blocked for some reason. Is there a way to do this in the JIRA Kanban board?

Among the things I thought about already:

Setting the issue as a Blocker is not what I want; that would just mean it should be prioritised.
Using a JQL query for an "is Blocked by" link could do the trick, but it would be nice to have something simpler.
There seems to be some plugins available, but my preference is on built in functions.

Accepted answers

Geert_Graat

Hi,

You could use the flags, although this actually represents an impediment: https://confluence.atlassian.com/display/AGILE/Flagging+an+Issue. Also, since JIRA Agile 6.6 you can add a field to your cards, so you could use a (custom) field to display that the issue is blocked.

Regards,

Geert

All comments

Geert_Graat

Hi,

Regards,

Geert

Eirik Midttun

Flags work well, just need a visual signal then the team to can decide on its meaning. Thanks a lot!

Reg Hawkins_qlak9y

Flagged is really useful the project managers love having a 2 dimensional filter showing all the flagged issues by fixVersion and I normally do this for the scrum teams based on Sprint's

Mitch Kent_53s1wa

We use a label, "blocked", and in the scrum boards we colour red any ticket with that label and also put a swim lane at the top of the scrum board for any tickets marked as blocked.

Am keen to find something less manual, but it works well enough.

Lance Nehring

Is it really not possible to mark a story as blocked by something else (another story, or bug)??

Reg Hawkins_qlak9y

You can use links and say an issues is blocked by another issue

Esther Strom

Yes, but there's no visual indicator on a board that a ticket is blocked or a blocker. For example, it would be cool if a ticket that's blocked by another would display something like this:

Esther Strom

As an update to my recent comment (and a possible answer, however late), I want to point out that Atlassian has very recently introduced a new JQL function called issueLinkType, which can be used in filters, but also in boards.

It's not perfect; if you're already using card colors for something else, you won't be able to use this as well. It also behaves inconsistently when a ticket has links of multiple types. But if you're looking for an easy way to get a view into what might be blocked, and what might have blockers, it works pretty well.

Lialia

You mean the red sign near the type of issue in the lower left corner, right?
It's a priority flag.
Just add priority called 'Blocker' or smth and select a suitable icon for it.

Dieter Band

Unfortunately, this marks tickets as blocked even if all the blocking tickets are marked resolved.

LinkedIssues(issueKey,CaseSensitiveLinkType) can only be used with a distinct issue key - is there a way to to do that in a more generic way?

Esther Strom

Like I said, it's not perfect But it's more than we had before. As to distinct issue keys, I don't know - you'd need to contact Atlassian about that. You could comment on the ticket that announced the new functionality, but I don't know if Atlassian pays attention to comments on closed tickets, as they have not responded to a comment I posted a month ago.

ETA that it's not native, but if you have ScriptRunner, you can use the enhanced search functionality to pull issues that have blockers that are still open, and vice versa.

This will display issues that are blockers in a project where the issue itself (the blocker) is not closed and where the parent issue isn't closed:


issueFunction in linkedIssuesOf("project = PHTP and status != Closed", "is blocked by") and status != Closed

And this will give you the reverse - show issues that are blocked, where the issues themselves are open and the issues doing the blocking are open:


issueFunction in linkedIssuesOf("project = PHTP and status != Closed", "blocks") and status != Closed

Dieter Band

Thank you, according to our admin, ScriptRunner will be installed in the near future, so that might be the solution ;-)

Scott Powell

project = ROC AND issueLinkType=Blocks

Includes both the blocking ticket and the tickets that it blocks. In other words, it includes "is blocked by" as well as "blocks."

Travis Christman

Feature suggestion:

As a product manager using JIRA, I want to have an indicator that when I tap it marks a ticket "blocked" so that I and reporting know that the ticket is blocked.

UAC

Indicator in tickets and bugs, that when I tap on it, it marks a ticket "blocked" so that I and reporting knows that the ticket is blocked.

notes: A separate ticket but worth mentioning a nice to have would be a notes field when when you tap on blocked.

This is a feature that an Atlassian competitor has today.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira