Blockers
A blocker marks work that cannot move until something else happens, such as a dependency, a decision, or missing input. It stays attached to the initiative, bug, pull request, issue, or todo that is stuck.
Add a blocker
Add a blocker from the Blockers column in your recap. The new item starts blocked and appears in team updates.
Mark existing work as blocked
Set the status to Blocked and explain why in the description or a comment. Include the dependency, owner, expected next step, and any linked todo, issue, or pull request.
Deploy load balancer improvements
Blocked by Gilfoyle's pending security audit and his insistence on "proper" SSL certificate management
Where blockers appear
Blocked work shows up in recaps, on boards, and in standups. Blocked issues from connected apps appear there too.
Review blockers before standup. If a blocker belongs to another team or person, assign it or mention them so they see it.