Overview

Beyond the standard filter buttons, task tables support a query language for precise filtering. On Tasks, click the { } icon inside the search box (Query with ScQL) to switch into query mode; click Close query to switch back. The same query bar is available on tickets, projects, and contacts tables.

A query is one or more conditions joined with AND and OR. Each condition is a field, an operator, and a value. The bar autocompletes field names and values as you type, so you rarely need to memorize anything.

Example queries

QueryWhat it finds
assignee = currentUser() AND due <= endOfWeek()Your tasks due by the end of this week.
status = "In Progress" AND priority IN (HIGH, URGENT)High-stakes work that is underway.
assignee IS EMPTY AND statusType != COMPLETEDUnassigned tasks that are not finished.
project = "Website Redesign" AND updated >= -7dTasks in one project touched in the last 7 days.
text ~ "payment bug"Matches name, description, and task number.
parent IS EMPTY ORDER BY due ASCTop-level tasks, soonest due first.
cf.budget > 5000Tasks whose custom field named budget exceeds 5000.

Fields, operators, and functions

  • Common fields: name, key (task number), status, statusType, priority, assignee, creator, project, sprint, group, type, parent, due, scheduled, created, updated, completed, storyPoints, estimatedHours, isPrivate, isArchived, isRecurring.
  • Operators: = and != for exact matches, ~ and !~ for contains, IN and NOT IN for lists, > >= < <= for numbers and dates, and IS EMPTY / IS NOT EMPTY.
  • Date helpers: functions like now(), startOfDay(), endOfWeek(), startOfMonth(), endOfYear() — each accepts an offset, so startOfWeek(-1) is last week. Relative durations also work: -7d, 2w, 1M.
  • User helper: currentUser() matches the signed-in user, which makes queries shareable between teammates.
  • Custom fields: prefix the field name with cf. to filter on custom fields.
  • Sorting: add ORDER BY with a sortable field and ASC or DESC.

Helpers next to the bar

  • Visual builder: compose conditions from dropdowns if you prefer not to type the syntax.
  • Describe it in English: type what you want in plain language and Scrambl drafts the query for you.
  • Saved queries: save queries you run often and share a link to the exact query with a teammate.

Best practice: Build a query once, then save it. Saved queries plus currentUser() give every teammate the same lens on their own work.

Next steps

  • Turn a great query into a shared view — see the task views article.
  • Filter on your own fields with the cf. prefix — see custom fields and columns.