Type / or use the search icon in top navigation to search goals, KRs, initiatives and comments.
System fields
| Search operators | What it will match |
|---|---|
| foo bar | Match all items that contain “foo” and “bar“ |
| “foo bar” | Match all items that contain the phrase “foo bar“ |
| created:2020-01-01 created:today created:yesterday created:”5 days ago” created>2020-01-01 created>=”2 days ago” | Match all items created on the given date (YYYY-MM-DD). You can also use natural language dates. Moreover, comparisons (>, >=, <, <=) also work for date fields. |
| updated:2020-01-01 | All items updated on the given date. Other date operators will also work. |
| last_comment_on:yesterday | Last comment date on a goal or initiative |
| owner:ram,shyam | All items belonging to either Ram or Shyam (either first or last name can be used, email address can be used to break ties) |
| team:dev | all items under the team “dev” |
| due<=2022-03-31 | Items with a due date before the given date. Other date operators will also work. |
| closed>”7 days ago” | All items closed after a certain date. Other date operators will also work. |
| status:”not started” status:”in progress” status:in-progress status:behind status:”at risk” status:done status:in-progress,behind | All initiatives with the given status. If a comma separated list of statuses is given, any initiative matching any of these statuses will be returned. |
| priority:high priority:mid priority:low priority:high,mid | All initiatives with the given priority. If a comma separated list of priorities is given, any initiative matching any of these priorities will be returned |
| created>2022-01-01 status:”in progress” priority:high | If multiple search queries are provided, only initiatives that match all of these will be returned. |
Custom Fields
Custom fields can be used as search operators too. To use a custom field as a search operator, transform its name as follows:
- Prefix “cf_” to the name
- Lowercase the name
- Replace every space with an underscore
- Remove all non-alphanumeric characters
So, a custom field name like:
“QA Review Date” transforms to “cf_qa_review_date”,
“Task-Id” transforms to “cf_taskid”
| Search operator & example | What it will match |
|---|---|
| cf_qa_review_date:today | All item’s where the custom field “Qa review date” has been set to today. |
| cf_stage:”design,dev started” | All item’s where the custom field “Stage” has been set to “Design” OR “Dev Started”. |
| cf_stage:design,designdone cf_sprintid:1.1 | All item’s where the custom field “Stage” has been set to “Design” OR “Design Done”. and all items where “Sprint ID” is “1.1” |
Sorting
Search results can also be ordered using the order_by operator.
| Search operator & example | What it will match |
|---|---|
| foobar order_by:created | Find all search items containing the term “foobar” and sort the results by creation date in ascending order |
| order_by:-created | Sort results by creation date in descending order |
| order_by:cf_stage | Sort results by the values of the custom field called “Stage”. If the custom field is of type dropdown, then results are sorted according to the order in which the field’s values are defined. |