Write the relevant update
Owner role · Collaborator
Evidence: The note distinguishes checked behavior from the pending decision.
Command-line workflows / Task collaborators
CLI walkthroughPrepare a Markdown task comment that contributes evidence or a decision request, then inspect its posting target.
Use a bounded update rather than duplicating the full task description.
Opens the current invite-request page. Access is subject to approval; this example is not imported automatically.
Illustrative case: a reviewer needs a concise note explaining which behavior passed and which decision still blocks acceptance.
teamboost comments list --task TB-120 --org ORGANIZATION_ID --environment production --json --no-input
teamboost comments add --task TB-120 --content "Acceptance evidence ready; boundary decision still pending." --dry-run --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 · Collaborator
Evidence: The note distinguishes checked behavior from the pending decision.
Owner role · CLI user
Evidence: The preview identifies the intended task and complete comment content.
Owner role · Task owner
Evidence: Saved comment evidence is read back before reporting it as published.
Decision to make: Preview the comment on the verified task; post only when the communication is authorized.
Invented planning text. Adapt it to your evidence and confirmed owners.
The checked behavior is ready for review. The date-boundary decision remains unresolved; please confirm the intended rule before acceptance. Link actual evidence in the real task.
From a useful outline to team work
Review the bounded update before using the TeamBoost CLI comment workflow; the example does not post a comment. 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.
The source supports --content-file - for UTF-8 Markdown input.
The packaged command map does not supply comment edit, reply or delete commands.
No. The brief is a manual planning resource. Use the product access link to check onboarding and the workflows available in your account.