We have defined a status called "Stalled". Once somthing is stalled, it moves there. Problem is that one looses the context, in which status is it stalled?
Before, in the Classic board, there was this conecpt of "sub-status", where one could "tag" a ticket to be stalled.
Add a customfield, e.g Multi checkbox called Stalled.
Add Swimlane based on Queries and enter a JQL query, e.g. Stalled = Yes
When an issue is stalled, check the checkbox for Customfield Stalled.
Then you have a swimlane with all stalled issues
AFAIK, you cannot have sub-status as a standard field. However, you can either add a custom field which says whether the issue is stalled or not or create the Stalled status and add a custom field which will hold the last status, but in this case you will need some workflow scripting plugin (to provide a condition) to get it back to that status.
Thanks, that is possible, yes, but it is a workaround. And when displaying it in boards and such, it will be cumbersome to visualize it.
From my perspective, conceptually, something is stalled inside another status. Stalled is not a status of itself.
You can use a flagging field and do not have to change the status.
The issues will end up under a Swimlane in the rapid board.
According to this  it's not yet possible with the rapid boards, but it seems like it will be available soon.
Atlassian Summit is an excellent opportunity for in-person support, training, and networking.Learn more
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