should blocked be a status or some kind of atttribure

[Elaine Cawthorne]

we are setting up a new workflow and were going to have blocked as a status but someone pointed out that in doing this you lose the feeling of where the item is as it could be in progress and perhaps waiting for UAT resources or it could be upstream and waiting fom clarification. What do other people do?

[Deleted user]

Our team uses the built-in flag option. You can right click on a story from the sprint/kanban board to add a flag and a comment. The flag is used to mark impediments in jira.

If you flag an issue, the status doesn't change. It says in the same place on the board, but gets a little flag icon and the issue card turns a light yellow.

Here's more info from Jira's documentation:

https://confluence.atlassian.com/jirasoftwarecloud/flagging-an-issue-777002748.html

[Elaine Cawthorne]

that sounds exactly like what we are looking for (very rare with Jira!) thank you 

[Elaine Cawthorne]

any idea how we could force the user to type a reason when the flag is set?

[Deleted user]

If you are just adding a flag and not transitioning the issue to a status called "Blocked," I don't believe there is a way to require a comment. 

It's best to get your team into the habit of adding a comment. We usually @ someone in a comment if we see something blocked without a reason. We also usually comment on our impediments with something like "BLOCKED because XYZ reasons" so that comment stands out a little.

[张肖]

We also encountered the same problem.
And this sounds exactly like what we are looking for :-) 
What a clever way!