Many times my users ask me to add "sometimes" status, like "On Hold", "TBD" etc. What is the best workflow configuration for that? Back and forth transitions? Looks like spaghetti to be honest...
Appreciate all suggestions :)
Yes, back and forth transitions, but keep it very simple, having only one "held" type status. I'd stick with "On hold", and while I'd let people put it on hold from most status in the workflow, I'd generally only let it go back to early "to do" type status in the flow to show that more work needs to be done on it and the restart process is not trivial (If you want to be able to go to where it was put on hold, then there are some handy add-ons that can provide "only allow transition based on the transition that took me to on-hold")
"TBD" is a natural part of the workflow though, and frankly simply means "to do" to me. If it needs discussing, then you've not started on it, so leave it in to-do. I would question any process that has "sometimes" status in detail (why is it not going back to simply "to do"?), and even if the users insist, never allow more than "blocked" or "held for business reasons".
And, yes, it will look like spaghetti. It's why I avoid allowing held status.
I'm trying to avoid both, useless statuses and spaghetti transitions, but users sometimes have needs. It's not only On hold, but also 10%-90% process (only 10% cases are different), so they need more options. They are focused on the status especially when the workflow is moving across the teams. If this is important for them, I just agree :)
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