Kanban principle of Visibility - Blocked

[Chambers_ Matheu _WP_]

I cannot believe that on the Jira Kanban board (by default) a blocked story has ZERO visible effect on the card layout...!

The Kanban principle is based on visibility...!

There is a second option of a "flag", but this doesn't really fit, as it can be used for any reason.

How do users get round this...? and WHY is this not core functionality...?

[Rudy Holtkamp]

Hi @Chambers_ Matheu _WP_ ,

How do you determine if a story is blocked or not?

If you know that logic, you are able to add a visual indicator in the summary, with the help of an automation rule. You can e.g. add a ⛔icon in front of the summary, so you can easily see this on your Kanban card.

[Dave Mathijs]

HI @Chambers_ Matheu _WP_ Welcome to the Atlassian Community Forums!

In addition to Rudy's answer, you can also configure card colors:

Configure card colors

You can base your card colors on work types, priorities, assignees, or JQL. Colors are configured per board (not globally).

To add color:

1. If not already there, navigate to your company-managed software space.

2. Select the Active sprints view (if you use a scrum board) or the Kanban board view (if you use a kanban board).

3. Next to your board’s name in the sidebar, select More actions (•••), then Board settings.

4. Expand Layout in the sidebar, then select Card Colors.

5. Select method from the drop-down.

6. Select the square in the Color column, and pick a color for the work type, priority, assignee, or query. You can switch between methods, and your settings will be retained.

To edit or remove colors from a query, select More actions (), then:

1. Edit the card color or update the query.

2. Delete the card color to remove the color and make it usable for other queries. Any work items that used that color will restore to the default when you reload your page.

3. Reorder a card color by dragging and dropping the dotted grid icon () to a new position.

For query-based colors, the order is important as each work item will be colored according to the first query it matches.

For each method, you can apply one color for item. For example, pick one color for each work item type, priority, assignee, or query.

The colors display as a thin strip on the left-side of the cards on your board.

[John Funk]

Hi Matheu - Welcome to the Atlassian Community!

Just because the Flag can be used for other interpretations by your organization doesn't mean that it doesn't meet the need for Blocked functionality. I would argue it does but also gives flexibility to be used for other purposes if desired. 

Like most things, including status names, it depends on how your organization, or even team, defines the use of it. So, Flag is perfect for the functionality of Blocked. If you Flag a card on a board, there is no doubt it is blocked visibly. Which is what you are going for. Also, behind the scenes, most time in status apps/functionality use the Flag functionality to stop the clock for delay calculation, which is also a Kanban functionality. 

So, I suggest you use the Flag and enjoy all that it gives you.  :-)

[Bill Sheboy]

Hi @Chambers_ Matheu _WP_ -- Welcome to the Atlassian Community!

Yes, and...to the great suggestions to make blocking / impediments visible with Flags, card colors, and / or automation updates to a field / indicator.

A variation which builds upon those is using swim lanes with JQL, where:

1. the top swim lane is always any expedited items,
2. the next swim lane is any blocking items, and
3. remaining swim lanes, as needed by the team, to help manage the value stream.

The one approach I would not recommend is adding a "blocked" status to the team's workflow on the board such as with a separate column.  In my experience, that will lead to unintended consequences such as making blocking a normal thing rather than an exception...reducing the incentive for the team to rapidly address blocking to improve flow and value delivery.

Kind regards,
Bill