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.
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.
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.
Hey admins! I’m Dave, Principal Product Manager here at Atlassian working on our cloud platform and security products. Cloud security is a moving target. As you adopt more products, employees consta...
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