List tasks owned by me and call them “tasks I created.”
Command-line workflows / Team analysts
Before / afterSeparate task creator from delivery owner
Choose the correct task filter when a question concerns who requested work versus who is responsible for it.
An origin question and a delivery question can return different task lists. Keep both relationships visible when reviewing who requested work and who is expected to complete it.
Opens the current invite-request page. Access is subject to approval; this example is not imported automatically.
Compare the decision quality
Illustrative before / afterIllustrative request: “show tasks I created.” Several of those tasks are owned by colleagues, while other tasks assigned to the requester were created elsewhere.
Use the creator filter and state that the result concerns task origin, not current ownership.
Identify the subject
Owner role · Analyst
Evidence: The question explicitly distinguishes created by from assigned to.
Choose the matching filter
Owner role · CLI user
Evidence: The read uses --creator me or --owner me according to that subject.
Explain the result boundary
Owner role · Reviewer
Evidence: The answer states which relationship was filtered and its pagination coverage.
Decision to make: Use the creator constraint for origin questions and the owner constraint for delivery responsibility.
Filled illustrative planning example
Invented planning text. Adapt it to your evidence and confirmed owners.
Synthetic records: W-17 was created by Morgan and is owned by Lee; W-18 was created by Lee and is owned by Morgan. For Morgan, a creator query concerns W-17 and an owner query concerns W-18. These are illustrative relationships, not live records.
Put the outline to work
- Ask whether the requester means tasks they created, tasks they own, or the intersection; write that subject in the review brief.
- Inspect the installed creator and owner filter contracts, resolve the subject in the intended organization, and preserve the requested project restrictions.
- Label the returned list with the relationship and pagination covered; do not describe created work as assigned work.
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
Is creator a responsibility assignment?
No. It records origin; ownership concerns responsibility for moving the work forward.
Can a task have different people in these roles?
Yes. Read the actual fields rather than inferring one from the other.
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.