Reference
List tasks
The list-tasks tool, and the REST call it is generated from.
Filters compose. status is what somebody asserted and state is the computed readiness; asking both finds where they disagree.
ref_url is every task citing any of those URLs, compared normalised — the check to make before creating anything.
Rows carry no body: get-task reads the whole task.
Parameters
- project
Only these
proj_…ids (repeat or comma-separate); omit for all of yours. One you are not a member of answers404. - status
Filter by where the work is. Repeat or comma-separate.
- kind
Filter by what the node is;
kind=projectlists the goals. Repeat or comma-separate. - priority
Only these levels;
noneis the tasks nobody prioritised. - state
Only these computed readiness states.
- tag
Tasks carrying any of these tags.
- ref_url
Only tasks citing any of these URLs, compared normalised. Repeat it for several; never comma-separate. Each row's
matched_refsnames the URLs it cites as you sent them, so one read checks a batch for duplicates. - query
A title containing it or two of its distinctive words (all, for a shorter query), or a body matching it in words or meaning. Titles first, the whole query before a few of its words.
- assignee
Whose:
me(you and your teams),none, auser_…orteam_…. - linked
false: only tasks with no link of any kind, in either direction, to an open or a closed task.true: the rest. - limit
Defaults to 50. For more, follow
next_cursor. - cursor
The
next_cursorof the previous page, with the same filters.
Responses
Generated from the spec this operation is implemented against, so the two names above cannot disagree with the surface a client sees.