How to mark an issue as done for a specific Kanban column

Hi, our team uses JIRA Agile to visualize our Kanban process, we have lots of columns, but for brevity let's assume that there are "Backlog", "Implementation", "Review" and "Done". Back when we used a paper Kanban board a developer would mark an issue that he implemented with a green sticker, so that the other devs could see which issues they could pull into the next column (Review). What would be the best way to do this in JIRA Agile? Flagging the issues is not really an option since we use flags to show that there is a problem with an issue.

We have tried the following:

  • An additional "Implementation done" column, but that creates an unwanted buffer, increases the total WIP-Limit and makes the board way bigger that necessary if you have many columns already.
  • A Custom "Kanban step done" field on the issues, but that was complicated to set (edit the issue, update the field, save the issue) and since custom fields cannot be updated by post functions we had to undo all that manually once an issue was pulled into the next column.
  • (Our current solution) An extra "Kanban step done" resolution which we used like the custom field. It has the advantage that the resolution can automatically be reset by a post function when the issue is pulled into the next column, but resolving an issue multiple times half-way through the process feels wrong.

At this point, I guess the answer is either something simple that we all have overlooked or that functionality just doesn't exist in JIRA Agile, which would be strange. 

1 answer

1 accepted

This widget could not be displayed.

Why would the developer not push the issue to the "Review" column/status as soon as it is ready for Review, i.e. "implementation done"? It now sits in that queue, right?

If you need an extra status, how about "Waiting on Review" and map that to the same 'Review' column as "Review in Progress"? 

Pushing to the next Column would be against the Kanban principle of pulling your work and would only move the problem one step further.

However, using two statuses in the same column is a rellay good idea that I hadn't thought about yet. I'll talk to my team and try it on Monday, thanks.

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted Tuesday in Jira

What modern development practices are at the heart of how your team delivers software?

Hey Community mates! Claire here from the Software Product Marketing team. We all know software development changes rapidly, and it's often tough to keep up. But from our research, we've found the h...

95 views 1 2
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you