Search project titles
Owner role · Contributor
Evidence: The project list returns candidate names and references in the selected workspace.
Command-line workflows / Project contributors
CLI walkthroughResolve a project name before task filtering
Discover the intended project and stable identifier before applying project scope to a task request.
Resolve a project container before narrowing a task list. A familiar project name is a search clue; the stable identifier and agreed purpose determine the scope.
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 examplesIllustrative case: two projects contain “Platform” in their title, but the task request concerns only one.
teamboost projects list --search Platform --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.
Resolve the ambiguity
Owner role · Requester
Evidence: The intended project is confirmed using its context, not list position.
Carry scope into the read
Owner role · CLI user
Evidence: The task request retains the verified project ID and original filters.
Decision to make: Confirm the intended project candidate, then use its identifier for the task read.
Filled illustrative planning example
Invented planning text. Adapt it to your evidence and confirmed owners.
Synthetic candidate A: Platform API, purpose contract delivery. Candidate B: Platform Operations, purpose service maintenance. Request: review the API contract backlog. Resolution: A, after requester confirmation. ORGANIZATION_ID in the displayed command is a placeholder to replace with verified context.
Resolve the candidate before reading tasks
Illustrative project names demonstrate the choice; actual references come from scoped discovery.
One confirmed project
- Next action
- Carry its verified identifier into the task read.
- Evidence to revisit
- The requester agrees the project purpose and scope.
Several plausible projects
- Next action
- Ask which purpose matches the request; do not choose the first result.
- Evidence to revisit
- A confirmed candidate is still missing.
No matching project
- Next action
- Report the missing match before proposing any new container.
- Evidence to revisit
- The requester decides whether the intended project exists.
Put the outline to work
- Search Platform in the intended organization and retain each candidate name and stable reference.
- Ask the requester to distinguish Platform API from Platform Operations using the project purpose; stop with an unresolved question if neither can be confirmed.
- Use only the confirmed reference in the subsequent task read, keeping owner and status constraints unchanged.
From a useful outline to team work
Explore TeamBoostAI for your team
This manual brief helps an authorized TeamBoost CLI user keep identity, query scope and review evidence explicit. Check the installed interface and account access before using a source-backed command. 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
Does title search guarantee an exact match?
No. Inspect candidates and the documented title-search behavior.
What if no project fits?
Report the missing match; do not silently substitute a similarly named project.
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.