Searching in Shortcut: Using Search Operators

Story search queries will look for matches in Story titles, descriptions, and comments. By default, all queries will use AND logic when combining multiple operators (OR logic is not available in Search at this time, but it is available when filtering on the Stories page).

There are two categories of search operators available when searching for Stories: Story-specific search operators (which will find results only for Stories), and general search operators (which will find results for both Stories and Epics).

 

Story-Specific Search Operators

 

type: Finds all Stories of a specific type (feature, bug, or chore). A query that contains more than one unique type operator will yield no results.
estimate: Finds all Stories of a specific point value. This is a numeric value, i.e. estimate:4. See our Estimate Scale article for more information about point estimations.
team: Finds all Stories associated with a specific Team. Enter the Team's mention name (without a leading @) directly following team:ie team:growth
has:attachment Finds all Stories with attachments. This operator only searches for attached files, not anything pasted or uploaded in comments

has:task

Finds all Stories with tasks

has:epic

Find all Stories added to an Epic

has:branch

Find all Stories that have a VCS branch associated

has:commit

Find all Stories that have a VCS commit associated

has:pr

Find all Stories that have a VCS pull request associated

branch:

Find all Stories that have a VCS branch with the given name associated

commit:

Find all Stories that have a VCS commit with the given full hash or url associated

pr:

Find all Stories that have a VCS pull request with the given number or url associated

is:blocked

Finds all Stories that have been marked using Story Relationships as blocked by another Story
is:blocker Finds all Stories that have been marked using Story Relationships as blocking another Story.
is:story

Returns only Stories in search results.

 

General Search Operators 

id:

  • id:123

title:

Searches Story and Epic titles:

  • title:hello will search for "hello" in titles of stories and epics.
  • title:"hello world" will search for "hello world" in titles.
  • title:hello world will search for "hello" in titles  AND "world" in titles/descriptions/comments.

description:

Searches Story and Epic descriptions:

  • description:hello will search for "hello" in description of stories and epics.
  • description:"hello world" will search for "hello world" in descriptions.
  • description:hello world will search for "hello" in descriptions AND "world" in titles/descriptions/comments.

comment:

Searches Story and Epic comments.

  • comment:hello will search for "hello" in comments of stories and epics.
  • comment:"hello world" will search for "hello world" in comments.
  • comment:hello world will search for "hello" in comments AND "world" in titles/descriptions/comments.

project:

Finds Stories in a specific Project (may use the Project name or Project ID). Or Epics with stories in a specific Project. For best results, queries for multi-word Project titles should be placed in double-quotes.

  • project:frontend
  • project:"growth hacks"

 

epic:

Finds all Stories in a specific Epic. For best results, queries looking for an exact match should be placed in double-quotes.

  • epic:growth will find all stories in epics that contain "growth" in their title
  • epic:"growth hacks"

 

objective:

Finds all Stories in the Epics within a specific Objective. For best results, queries for multi-word Objective titles should be placed in double-quotes.

 

state:

Finds all Stories in a specific Workflow state. For best results, queries for multi-word workflow state titles should be placed in double-quotes.

  • state:"ready for dev"
  • state:completed

 

Searching across Workflow States with is:

In addition to the state: operator, the following operators search over the different types of workflow states.

Since stories can only have one workflow state, using more than one of these operators can yield no results.

  • is:unstarted
  • is:started
  • is:done

label:

Finds all Stories or Epics with a specific Story label. For best results, queries for multi-word labels should be placed in double-quotes.

  • label:"needs copy"
  • label:release

Note: Stories in an Epic do not inherit the Epic labels.

 

owner:

Finds all Stories or Epics owned by a user. This query requires the user's full mention name (also known as their @-name) to work. Do not include the @ symbol at the beginning of the mention name.

Suggestions will be provided once the first few letters are typed.

  • owner:johnsmith
  • owner:bartsimpson

 

requester:

Finds all Stories or Epics requested by a user. This query requires the user's full mention name (also known as their @-name) to work. Do not include the @ symbol at the beginning of the mention name.

  • requester:johnsmith
  • requester:bartsimpson

 

Inversions and Exclusions

Of note, you can search for the inverse or exclude an operator by adding an ! or - in front of the operator. This is equivalent to a NOT boolean operator.

For example, i.e. !has:comment and -has:comment will return Stories with no comments.

 

Dates and Date Ranges

First, it's important to use the correct date formatting in your searches. The format Shortcut recognizes is 4 digit year-2 digit month-2 digit day:

  • YYYY-MM-DD

When searching for a date range, separate your dates with two periods:

  • YYYY-MM-DD..YYYY-MM-DD

You can make your date range open-ended (or unbounded, in search parlance) by adding an asterisk (*) on one side of the range. 

An asterisk on the left side of the date range would find you all Stories before the specified date:

  • *..YYYY-MM-DD

And an asterisk on the right side of the date range would find you all Stories after the specified date:

  • YYYY-MM-DD..*

You can also search using the terms yesterday and today, as well as tomorrow (but this latter term can only be used when searching for due dates, more on this below).

Please note that numerical date values and date terms currently can't be mixed -- so a search for   2018-04-01..today is not valid.

 

Date-Based Operators

You can search for Stories that have been created, updated, completed, or moved using a specified date or date range, or the terms yesterday or today.

You can also search for Stories that are (or were) due on a specified date or date range, or using the terms yesterday, today, or tomorrow 

  • created:2023-01-01
  • updated:today
  • completed:yesterday
  • moved:*..2023-02-01
  • due:tomorrow

When using the updated: operator, keep in mind that it asks "What Stories or Epics were last updated on/before/after this date or within this date range?"

The moved: operator will only find Stories that have changed workflow state (i.e., those which have "moved" to a different workflow state column) on or within a specified time period.

 

The `has:` Operators

  • has:comment - Finds all Stories with comments.

  • has:label - Finds all Stories with a label.

  • has:deadline - Finds all Stories with a due date.

  • has:owner - Finds all Stories with an owner.

The `is` Operators

  • is:unestimated - Finds all Stories with a point value of 0 (in other words, Stories with no point estimation).

  • is:overdue - Finds all Stories with a due date in the past.

  • is:archived - Finds all archived Stories.

Updated

Was this article helpful?

1 out of 2 found this helpful

Have more questions? Submit a request