# Search Operators Find Stories, Epics, Objectives, and Iterations using keywords, filters, and search operators. ## Overview Open Search from the search box at the top of the UI, or press the keyboard shortcut `/` to jump straight in. Select **Advanced Story Search** to access a detailed view of Story results. Search queries match against titles, descriptions, and comments. Results are ranked by relevance. Multiple operators in a single query use AND logic — all conditions must be true. ## Operators Search operators let you filter results by type, state, ownership, dates, and more. There are two categories: **Story-only operators** that return only Stories, and **general operators** that return results across Stories, Epics, Objectives, and Iterations. ### **Filtering by Type and Estimate** | Operator | Description | | ---------------------------------------- | ---------------------------------------------------------------------------- | | `type:feature`, `type:bug`, `type:chore` | Stories of a specific type. Only one type operator per query. | | `is:story` | Return only Stories. | | `is:epic` | Return only Epics. Combine with other operators: `is:epic team:Engineering`. | | `estimate:4` | Stories with a specific point value. | | `is:unestimated` | Stories with no point estimate. | ### **Filtering by State** | Operator | Description | | --------------------------------------- | ------------------------------------------------------------- | | `state:"ready for dev"` | Stories of a specific type. Only one type operator per query. | | `is:unstarted`, `is:started`, `is:done` | Stories and Epics in any Workflow State of that category. | | `is:blocked` | Stories marked as blocked by another Story. | | `is:blocker` | Stories marked as blocking another Story. | | `is:overdue` | Stories with a due date in the past. | | `is:archived` | Archived Stories, Epics, Objectives. | ### **Filtering by Entity Association** | Operator | Description | | ---------------------- | ------------------------------------------------------------------------------------------------------------------------------------------ | | `epic:growth` | Stories in Epics containing "growth" in the title. Use double-quotes for exact match: `epic:"growth hacks"`. | | `objective:"Q1 Goals"` | Stories in the Epics within a specific Objective. Double-quotes for multi-word names. | | `team:Engineering` | Stories, Epics, and Iterations associated with a Team. Use the Team's display name (not mention name). Double-quotes for multi-word names. | | `label:release` | Stories or Epics with a specific label. Double-quotes for multi-word labels. Stories in an Epic do not inherit the Epic's labels. | ### Filtering by Users | Operator | Description | | --------------------- | ------------------------------------------------------------------------------ | | `owner:johnsmith` | Stories or Epics owned by a user. Use their full mention name (without @). | | `requester:johnsmith` | Stories or Epics requested by a user. Use their full mention name (without @). | | `has:owner` | Stories with at least one owner. | ### Filtering by Metadata Attributes | Operator | Description | | -------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------- | | `id:123` | Find a specific entity by ID. | | `title:hello` | Search titles of Stories, Epics, Objectives, and Iterations. Wrap phrases in double-quotes: `title:"hello world"`. | | `description:hello` | Search descriptions of Stories, Epics, and Objectives. Wrap phrases in double-quotes. | | `comment:hello` | Search comments on Stories and Epics. Wrap phrases in double-quotes. | | `has:epic` | Stories added to an Epic. | | `has:comment` | Stories with comments. | | `has:task` | Stories with Checklist items. | | `has:label` | Stories with a label. | | `has:deadline` | Stories with a due date. | | `has:attachment` | Stories with attached files (not content in comments). | | `has:pr` | Stories with an associated VCS pull request. | | `pr:42` | Stories with a specific VCS pull request (number or URL). | | `has:branch` | Stories with an associated VCS branch. | | `has:commit` | Stories with an associated VCS commit. | | `branch:feature-x` | Stories with a specific VCS branch name. | | `commit:` | Stories with a specific VCS commit (full hash or URL). | | `skill-set:`, `product-area:`, `technical-area:`, `priority:`, `severity:` | Filter by Shortcut-defined Custom Fields. _Note: Advanced Custom Fields cannot be used as search operators at this time._ | Note: An unquoted multi-word value splits across fields. For example, `title:hello world` searches for "hello" in titles AND "world" across titles, descriptions, and comments. ### Inversions and Exclusions Prefix any operator with `!` or `-` to negate it. This is equivalent to a NOT operator. | Operator | Description | | ------------------------------------------- | --------------------------------- | | Example: `!has:comment` or `-has:comment` | Returns Stories with no comments. | ### Dates and Date Ranges Use `YYYY-MM-DD` formatting (4-digit year, 2-digit month, 2-digit day). #### Date operators: | Operator | Description | | --------------------- | ---------------------------------------------------------- | | `created:2024-01-01` | Stories created on, before, or after a date. | | `updated:today` | Stories or Epics last updated on a date or within a range. | | `completed:yesterday` | Stories completed on a date or within a range. | | `moved:*..2024-02-01` | Stories that changed workflow state on or within a range. | | `due:tomorrow` | Stories with a due date matching the value. | #### **Date range syntax:** | Pattern | Meaning | | -------------------------------- | ------------------------------------------------ | | `YYYY-MM-DD..YYYY-MM-DD` | Specific date range | | `*..YYYY-MM-DD` | On or before a date | | `YYYY-MM-DD..*` | On or after a date | | `yesterday`, `today`, `tomorrow` | Relative dates (tomorrow only works with `due:`) | Note: You cannot mix numerical dates with relative terms (e.g., `2024-01-01..today` is not valid).