Because that's over-complicated.
As a user, I want to know where my issue is in the process. "it's in analysis" is a good answer. "it's in analysis doing" or "analysis done" is a bad answer when they're part of "analysis". Which is it, and why are they different?
As a developer, what's the difference between "analysis - done" and "development - doing"? We've analysed it, so it's in the backlog. Why is there an extra step to push from analysis to dev? (And that's a question that applies across your whole diagram)
I'm afraid your picture represents a broken process. It's one that looks sort of ok from a human point of view, but in realistic terms, it's wrong and doesn't really work out.
I have to disagree with Nic. It's not over-complicated. kanban is a pull process. So there is no extra step of "pushing it from analysis to development". Rather the developer pulls the task as soon as he is ready to start.
There is also a clear difference between "analysis - done" and "development - doing", because it might depend on the results of the analysis if the task even gets to development. Also keep in mind that there might be several people with separate responsibilities involved. An analyst, a developer and a manager who decides based upon the results provided by the analyst if the task is to be taken up by development.
For me there is not enough information to say if the process is broken or not, but it could certainly work out.
As to why this feature does not exist, I do not have an answer, but I think it would be valuable to have it.
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot