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:
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.
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.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
Every time you release software, there's a bit of risk – that there's a bug, that something breaks, or that the feature doesn't resonate with customers. Feature flagging helps make high stakes s...
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!
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