The reason I've given a flat "no" here is that I've seen this implemented in all sorts of ways... and they all end up editing the workflow in the long run. Which means loads of ways to show "roadblocked", but none of them sticking with the default workflow.
The reason is simple - an issue that is "blocked" in some way is almost always best represented with a specific status meaning "we'd work on it if we could, but we can't". Even the places that started out and stuck with a more simple flag (e.g. a label or custom field saying "roadblocked", or a link to an issue that is blocking it ) ended up wanting to use the flag to say "cannot progress this", which leads to a condition on the workflow.
Also, you'll find most people want a clear and distinct way to show "blocked", because it can't be "in progress", "resolved", "open" etc when it's blocked - it's a very different state of play.
That said, I really do mean the workflow edits can be very very simple - add a step for "blocked", add in a couple of transitions in and out. Done.
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
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