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

OperatorDescription
type:feature, type:bug, type:choreStories of a specific type. Only one type operator per query.
is:storyReturn only Stories.
is:epicReturn only Epics. Combine with other operators: is:epic team:Engineering.
estimate:4Stories with a specific point value.
is:unestimatedStories with no point estimate.

Filtering by State

OperatorDescription
state:"ready for dev"Stories of a specific type. Only one type operator per query.
is:unstarted, is:started, is:doneStories and Epics in any Workflow State of that category.
is:blockedStories marked as blocked by another Story.
is:blockerStories marked as blocking another Story.
is:overdueStories with a due date in the past.
is:archivedArchived Stories, Epics, Objectives.

Filtering by Entity Association

OperatorDescription
epic:growthStories 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:EngineeringStories, Epics, and Iterations associated with a Team. Use the Team’s display name (not mention name). Double-quotes for multi-word names.
label:releaseStories 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

OperatorDescription
owner:johnsmithStories or Epics owned by a user. Use their full mention name (without @).
requester:johnsmithStories or Epics requested by a user. Use their full mention name (without @).
has:ownerStories with at least one owner.

Filtering by Metadata Attributes

OperatorDescription
id:123Find a specific entity by ID.
title:helloSearch titles of Stories, Epics, Objectives, and Iterations. Wrap phrases in double-quotes: title:"hello world".
description:helloSearch descriptions of Stories, Epics, and Objectives. Wrap phrases in double-quotes.
comment:helloSearch comments on Stories and Epics. Wrap phrases in double-quotes.
has:epicStories added to an Epic.
has:commentStories with comments.
has:taskStories with Checklist items.
has:labelStories with a label.
has:deadlineStories with a due date.
has:attachmentStories with attached files (not content in comments).
has:prStories with an associated VCS pull request.
pr:42Stories with a specific VCS pull request (number or URL).
has:branchStories with an associated VCS branch.
has:commitStories with an associated VCS commit.
branch:feature-xStories with a specific VCS branch name.
commit:<full-hash>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.

OperatorDescription
Example: !has:comment or -has:commentReturns Stories with no comments.

Dates and Date Ranges

Use YYYY-MM-DD formatting (4-digit year, 2-digit month, 2-digit day).

Date operators:

OperatorDescription
created:2024-01-01Stories created on, before, or after a date.
updated:todayStories or Epics last updated on a date or within a range.
completed:yesterdayStories completed on a date or within a range.
moved:*..2024-02-01Stories that changed workflow state on or within a range.
due:tomorrowStories with a due date matching the value.

Date range syntax:

PatternMeaning
YYYY-MM-DD..YYYY-MM-DDSpecific date range
*..YYYY-MM-DDOn or before a date
YYYY-MM-DD..*On or after a date
yesterday, today, tomorrowRelative dates (tomorrow only works with due:)

Note: You cannot mix numerical dates with relative terms (e.g., 2024-01-01..today is not valid).