TeamBoostWORKFLOW LIBRARY

Command-line workflows / Reporting owners

CLI walkthrough

Read beyond the first page of tasks

Continue a task query across pages while preserving filters and stating the coverage of the final result.

Distinguish observed distinct records from a reported total that may not be an exact count.

Request TeamBoostAI accessGet the work briefTask table (.csv)

Opens the current invite-request page. Access is subject to approval; this example is not imported automatically.

Work through the command boundary

Source-backed CLI examples

Illustrative case: a list shows ten tasks, but the request asks for all current in-progress work.

teamboost / example commands
teamboost tasks list --status IN_PROGRESS --page 1 --page-size 10 --org ORGANIZATION_ID --environment production --json --no-input

teamboost tasks list --status IN_PROGRESS --page 2 --page-size 10 --org ORGANIZATION_ID --environment production --json --no-input

Illustrative commands, not executed here. Replace ORGANIZATION_ID, example task keys and UUID placeholders with verified values. Read help in your installed version.

01

Preserve the query

Owner role · CLI user

Evidence: Each page keeps the same organization, filters and ordering.

02

Follow continuation evidence

Owner role · CLI user

Evidence: hasMore/nextPage is inspected rather than guessed from the page length.

03

Report coverage

Owner role · Analyst

Evidence: The summary distinguishes a complete traversal from a partial result or non-atomic snapshot.

Decision to make: Continue using the response pagination contract; deduplicate identifiers and stop clearly on failure.

Illustrative traversal note

Invented planning text. Adapt it to your evidence and confirmed owners.

Keep status=IN_PROGRESS and one workspace on every page.
Continue only when response evidence indicates more results.
If a page fails, label the answer partial and retain the last successful scope.

Put the outline to work

  1. Record the original query constraints.
  2. Follow continuation evidence and deduplicate stable IDs.
  3. Report interruptions and the observation scope without inventing an exact total.

Continue with a related decision

Command-line workflowsBuild a task summary from structured CLI resultsAsync reportingA weekly project summary that supports choices

From a useful outline to team work

Explore TeamBoostAI for your team

Use the TeamBoost CLI pagination example to inspect result coverage before calling a task report complete. Confirm the workflows available in your account before adopting this outline.

Request TeamBoostAI access

Opens the current invite-request page. Access is subject to approval; this example is not imported automatically.

Questions about this workflow

Is ten results the complete set?

Only if pagination evidence says there is no next page. Default page size alone proves nothing.

Can I trust reportedTotalElements as exact?

The source skill explicitly cautions that it is not an exact distinct-task count.

Does this create tasks in the product?

No. The brief is a manual planning resource. Use the product access link to check onboarding and the workflows available in your account.