Action search syntax

On the project actions list, the search box combines with the rest of the toolbar: you can mix free text and structured tokens, then narrow further with Assigned to me and, in Table view, the Statuses multi-select. In Kanban view, status is shown by column; search and assignee filtering still apply to which cards appear.

Tag filter (tag:)

Use tag: followed by text that should appear in a tag's name. Matching is case-insensitive and substring-based (the tag name only needs to contain what you typed).

• tag:customer — actions that have a tag whose name contains "customer".
• tag:"Steering Committee" — use double quotes when the tag name includes spaces so the whole phrase is one filter.
• Multiple constraints: tag:marketing user:me keeps actions tagged with something like "Marketing" that are also assigned to you. Add ordinary words to require those tokens in the action's searchable text (description, assignees, and related fields).

Assignee filter (user:)

• user:jane — matches actions assigned to a person whose display name, email, or name parts contain the text (partial match).
• user:"Jane Doe" — use double quotes when the assignee name includes spaces.
• user:me — matches actions assigned to you.

Workstream filter (workstream:)

Use workstream: followed by text that should appear in the workstream name. Matching uses the effective workstream for each action (manual assignment first, then tag-rule classification), case-insensitive and substring-based. See Workstreams for how assignments, tag rules, and unclassified actions work.

• workstream:platform — actions in a workstream whose name contains "platform".
• workstream:"Customer Onboarding" — use double quotes when the workstream name includes spaces.
• workstream:unclassified — actions with no effective workstream assignment.

Attention filters (attention:)

Use attention: followed by the signal you want. Only that category is kept — an unknown value matches nothing. Bare words overdue, at-risk, and quiet still work as shortcuts. Use the X on the search field to clear the query.

• attention:decision — actions that need a decision (Stuck). Also attention:"needs decision".
• attention:at-risk or attention:overdue — open work past its due date.
• attention:quiet — actions marked going quiet.
• attention:waiting — actions waiting on others.
• Combine with other filters: attention:decision user:me or quiet workstream:platform. Using more than one attention filter requires all of them.

What search includes

Free-text tokens (anything not starting with tag:, user:, workstream:, or attention:, and not an attention word such as overdue or quiet) match against action content and linked external IDs (for example an Azure DevOps work item ID, Basecamp to-do or card ID, or Jira issue key)—you do not need a special prefix or integration name. Use the status filter and Kanban lanes when you want to slice primarily by status.

Dedicated status: or date-token syntax is not documented as a supported query language today.

Press Enter in the search field to trim the query. Tag behavior in the editor is covered in Understanding actions.