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; } } }

Cannot drag issue on kanban board from one status to a different status

fmoor

I am new to JIRA Kanban. I am evaluating whether it will serve my team's needs. One of the requirements is that issues can be marked as blocked. We are not a software team and will not be tracking software development. We work on hardware. Our issues can be blocked if other groups or teams do not deliver hardware in time, or if the hardware does not work as advertised, which happens frequently in development of new products. If I look at the board Configuration -> Columns section I see that the In Progress column has a BLOCKED status. If I select an issue in a board the details show the status as IN PROGRESS but I can't change it to BLOCKED. If I try dragging the issue there is no box for BLOCKED. How do I change an issue's status to BLOCKED?

Accepted answers

Jared Dohrman [

Hi @fmoor,

The workflow that your issue type is using will need a transition from In Progress to Blocked. The Kanban board will also need to have the status mapped to the column (you can do this by Configuring the board, and clicking on columns, and then drag and drop the statuses to suit)

The trick is that you can only drag and drop between a column (one or more statuses) if there is a transition between the two statuses on the workflow status you are trying to drag from.

Thanks,

Jared.

All comments

Jared Dohrman [

Hi @fmoor,

The trick is that you can only drag and drop between a column (one or more statuses) if there is a transition between the two statuses on the workflow status you are trying to drag from.

Thanks,

Jared.

Nic Brough -Adaptavist-

There's a bit of a flaw in JIRA's implementation of the boards here. You can not drag an issue to another status in the same column. The boards only allow for a change of column.

A couple of options:

Use the "impediment" flag instead. (Probably not ideal for you, but I had to mention it)
Add another column to the board for "blocked" explicitly. (Less than ideal as another column looks like a valid part of the process, and "blocked" takes it out of the normal flow really)
Change the status in plain JIRA in the issue view, rather than on the board (less than ideal because you have to leave the board to do it)

Reg Hawkins_qlak9y

Have you tried this recently?

Nic Brough -Adaptavist-

Yes. Still not there, and Atlassian have stated they are not going to enable it.

PM_z610yc

I would recommend to create a user called 'Blocker' and assign issues that are blocked to this user. This way Issue will remain on the original column it was blocked. To make it more visible I recommend to add a warning sign image to blocker user profile picture. This will make these issues stand-out in the board.

Nic Brough -Adaptavist-

But now you don't know who it is assigned to. Worse, it's assigned to no real person, so you don't know who is responsible for it.

Really, this is a very bad idea.

Randy_dyxb6i

Although i've never done this or tried it, i like the idea of having a strong signal of a "blocked" assignee icon image on the card when it'd blocked.

The (major) downside as nic pointed out is that you'd have to find a different way to track who's "owning" the item and unblocking.

unknown

Instead of using a 'user' have a label "BLOCKED" then set a filter so that the color of the card changes when that label is used.

This maintains the separation and keeps the owner.

Dele Oyedepo

I think the best non-intrusive solution is to use the flag feature in Jira which is used for indicating impediments. When a story is blocked, from an Agile perspective is has an impediment. A not too ideal solution will be to create a new column, you will need Admin access to configure your workflow which will affect other teams or groups using Jira.

unknown

If you go the flag route you can have a quick filter look for flagged issues, or a swimlane.

Gabriel Louet

Can you measure the time a call has been flagged to understand how long a call has been blocked for?

Dele Oyedepo

If you hover over the story on your board you should see 3 yellow or red dots that indicate how long the issue has been in that status/stage/column.

You will need to enable this setting by going to Board settings of the board >> Card Layout and turn on "Days in Column". I'm assuming you are using the cloud version. This might not be located in the same location with other versions of Jira

Tracy A Stimac

We are using the Flagged (impediment) and then added a swimlane that queries for Flagged. This moves all the blocked stories to a separate swimlane making them very visible and they retain the column and the assignee.

Tracy A Stimac

Using Flagged also adds the Flag symbol to the card and changes the card color to yellow - allowing it to "pop" more.

Dele Oyedepo

Another benefit of using flagged is that it shows up on your dashboard (if you are using the Sprint Health Gadget) which increases visibility into all the impediments your project/team might currently have.

Humberto Nunez

Where can i find this impediment flag?

Liz Debes

Has anyone figured out a way to add a column for impediment to the view contained within an Epic?

I am trying to help project managers who are working with several team or other users who are not looking at a story on a kanban or scrum board see an issue is flagged. I want a high view of stories in an Epic that are blocked.

Dele Oyedepo

I’m not sure I totally understand what you mean by “ add a column for impediment to the view contained within an Epic?”

However, if the goal is to bring transparency and feasibility to issues flagged as impediments across multiple projects for those that are not involved in the day to day dealings of the teams, You can accomplish this in a couple of ways.

Create a dashboard for the PM’s, they will be able to see all issues in Jira flagged as impediments (Blocked). Here is the JQL for the filter (Flagged = Impediment), you can choose to filter by project and other criteria if you don’t want all issues in your instance displaying
Create a new Kanban board for the PM’s using the same filter or create a quick filter

I hope this addressed your question

Liz Debes

I think I will start my own thread on this topic, but I just joined the community thanks to a google search on this topic looking for a suggestion.

I am looking if there is a away to customize what displays in the columns under the section within an Epic that is called, "Issues in Epic." I want it so that other users who have view access and are not monitoring the specifics of several different projects (like in a dashboard or on a board or in a saved filter) can see a high level view of stories related to one project. We use Epics to house related stories on one specific project/initiative.

Issues in Epic.png

Dele Oyedepo

I don't think it's possible to add the flag of an issue to that screen at this point in time. I believe based on your ask, a dashboard will be a clean solution.

Brooke Miller_i1y0zi

This may be helpful to visualize blocked items via Card Coloring.

JQL for Blocked Color Issues.PNG

Andy Heinzer

I agree that Jared’s answer here is the correct answer to the original question. When dealing with boards in Jira Software, it is the workflow that controls which statuses can issue can move into.

So although the board might not let you move an issue into a particular status from another status, most often this is due to the way the workflow is setup for that issue. I’d recommend checking out Work with issue workflows if you are not familiar with changing workflows in Jira. You will need to be an admin within Jira in order to make changes to a workflow.

It could be that there is a workflow condition preventing you from making that transition, OR the workflow might not have an appropriate transition between those two statuses for your to execute.

Welcome!

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

Quick Links

Find more posts tagged with

jira

jira-software

jira-software-development