Filter the requested set
Owner role · Coordinator
Evidence: The read uses BLOCKED and HIGH only when both constraints were requested.
Command-line workflows / Delivery coordinators
CLI walkthroughFilter blocked tasks in the intended workspace and identify which condition needs an unblock decision.
Use status and priority filters without inferring a blocker cause from a label.
Opens the current invite-request page. Access is subject to approval; this example is not imported automatically.
Illustrative case: a coordinator needs to review high-priority blocked work, not every incomplete item.
teamboost tasks list --status BLOCKED --priority HIGH --org ORGANIZATION_ID --environment production --json --no-inputIllustrative commands, not executed here. Replace ORGANIZATION_ID, example task keys and UUID placeholders with verified values. Read help in your installed version.
Owner role · Coordinator
Evidence: The read uses BLOCKED and HIGH only when both constraints were requested.
Owner role · Task owner
Evidence: Current detail identifies the specific step that cannot proceed.
Owner role · Decision owner
Evidence: The update names the needed decision and its delivery consequence.
Decision to make: Read the filtered set, then inspect each material blocker before requesting help.
Invented planning text. Adapt it to your evidence and confirmed owners.
Requested set: high-priority blocked tasks in one verified workspace. Evidence still needed: the blocker condition on each relevant task. Next action: ask the role able to resolve that condition.
From a useful outline to team work
The TeamBoost CLI example uses exact task filters to collect blocked work, followed by a separate review of the blocker evidence. Confirm the workflows available in your account before adopting this outline.
Opens the current invite-request page. Access is subject to approval; this example is not imported automatically.
Use --owner me when that constraint belongs to the request; otherwise it would narrow the result incorrectly.
No. Follow the actual impact and incident procedure rather than treating priority as proof of an emergency.
No. The brief is a manual planning resource. Use the product access link to check onboarding and the workflows available in your account.