How do you keep task ownership clear when work moves between teams?

Question

One thing I’ve noticed with Kanban workflows is that the board can look organized while it’s still unclear who actually owns the next step.

This becomes more noticeable when work moves between teams or people. A card can be “In Progress” for days, but the real question is usually: who is responsible for getting it to the next stage?

I’m curious how other teams handle this:

* Do you assign one owner to every card?
* Do you change ownership as work moves between teams?
* How do you handle blocked work?
* Do you track how long cards spend in each stage?

I’ve been looking at a few Kanban approaches recently, including Otper, where the workflow is built more around clear ownership and delivery visibility. But I’m interested in how teams actually handle this in practice.

What works well for your team?

Josh · Answer

Good question @Abhishek P. What's worked for us, all native Jira:

One assignee, always, and it changes at handoff. The assignee is "who moves it next", not "who did most of it". Automate the handoff: on transition into a status owned by another team, clear the assignee or set it from a lookup table (status to team triage person). That way the card never sits "In Progress" under someone who's already moved on.

Catch orphans with a saved filter. For example statusCategory = "In Progress" AND (assignee is EMPTY OR NOT status changed after -5d) on a dashboard or a daily email subscription. That's the "who owns the next step?" list.

Blocked work. Flag the card and add a comment saying what it's waiting on. Flagged cards stand out on the board, and Flagged is not EMPTY gives you a blocked list.

Time in stage. Turn on "Days in column" on the board cards for the at-a-glance version. For trends, the newer Average Time in Status dashboard gadget (or the control chart on company-managed boards) shows which handoff is where work waits.

Tomislav Tobijas · Answer

I'd say there's no correct answer here @Abhishek P but it's a great topic and it's probably more common problem than people would think.

While every organization has its own unique process, Jira offers several built-in features to help with these exact scenarios. For example, many teams use Jira Automation to automatically change the Assignee when a work item moves to a new status, use the "Flagged" feature to clearly highlight blocked work, and enable the "Days in column" board setting to track how long cards sit in a specific stage.

I can say that we assign almost everything to specific people, apart from Epics, which it has been agreed internally that could float without Assignee. As for ownership, yeah… It's mainly the case that it changes as work item changes teams 👀

Again, you'd have to weigh your options ⚖️ and decide based on your requirements. Potentially try things out and see what works.

Cheers,

Tobi

Giorgi Meskhidze · Answer

One owner Giorgi Meskhidze