How do I search for tickets?

You can use the Ticket search icon to find tickets according to some keywords. By default, it will find all ticket matches that contain ALL of the words that are entered. Searching for "ruby rails" will find tickets matching both "ruby" and "rails" in the title or body.

The drop down list provides a few common custom searches to assist you:

  • My Tickets - Shows all tickets you are watching, the currently logged-in user.
  • All Tickets - No keywords provided, finds the most recently updated tickets.
  • Open Tickets - Find all tickets that haven't been resolved in any way yet.
  • Closed Tickets - Find all tickets that have been resolved, put on hold, or marked as invalid.

You'll also see entries to search for tickets assigned to other members of your team, or specific to a certain active milestone. There are some detailed search keywords that you can use for customized search results. Keywords should be entered after the query and follow this format: keyword:value keyword2:"value 2". As the example shows, any values with spaces must be surrounded by quotes.

watched - This shows what tickets you are currently watching. You can't search on other users' * watched tickets, so the only valid value is watched:me.

responsible - This lets you search for tickets that are assigned to the given person. You can enter the person's full name, or just their first name. Also, you can use "me" as a special keyword to find your own tickets. Use "none" as a keyword to find unassigned tickets.


  • responsible:"Ricky Bobby" - Display tickets assigned to a specific user, use quotes around a first and last name
  • responsible:rick - Search for tickets assigned to First name, no need for quotes
  • responsible:me - Displays all tickets assigned to me
  • responsible:none - Displays all tickets not assigned yet
  • responsible:any - Displays all tickets assigned to someone

reported_by - Similar to the responsible keyword listed above, this searches for tickets used that were reported by the given user.


  • reported_by:"Ricky Bobby"
  • reported_by:Will

milestone - This selects the ticket's milestone. You can either enter part of the milestone name, or use one of the two keywords "none" or "next." The "none" keyword will find tickets without a milestone. The "any" keyword finds tickets with any milestone. The "next" keyword will look at all scheduled milestones and finds tickets for the first scheduled milestone in the current project. You can also search for milestones based on the ID only.


  • milestone:"1.0 Launch"
  • milestone:none
  • milestone:next
  • milestone:id#123456

state - This filters on the ticket's current state. Valid states include new, resolved, hold, invalid. You can also use two special keywords: open (includes open and new tickets) and closed (includes resolved, hold, and invalid tickets). The special keywords only work within the scope of a single project, so you can't use them on account-level queries.


  • state:open
  • state:closed

importance - This filters on the ticket's importance. Importance are integers greater than 0.


  • importance:1
  • importance:<5 (Finds tickets with an importance less than 5)
  • importance:>1 (Finds tickets with an imortance greater than 1)
  • importance:>=2 (Finds tickets with an importance greater than or equal to 2)

tagged - This finds tickets matching the given tag. You can use it multiple times for multiple tags.


  • tagged:ruby
  • tagged:ruby,rails
  • tagged:rails tagged:"ruby on rails"
  • tagged:none - lists all tickets which have not been tagged

updated - This searches for tickets based on the date they were updated. It attempts to parse simple English strings.


  • updated:"1 month ago"
  • updated:"Jan 2007"

created - This searches for tickets based on their creation date, using the same format as updated.

Inverted Queries

Some of the above keywords let you specify inverted keywords with a not- prefix.

not-query - This finds tickets that don't match the given keyword.

not-responsible - Finds tickets that are assigned to someone else, or nobody.


  • not-responsible:me
  • not-responsible:rick
  • not-responsible:any

Yes, you can specify not-responsible:none, but since this is a double negative, you may be better off with just responsible:any.

not-reported_by - Finds tickets not reported by the given user.

not-milestone - Finds tickets not assigned to the given milestone.


  • not-milestone:next
  • not-milestone:"Launch Party"

not-tagged - Finds tickets without the given tag. You can use it multiple times for multiple tags.


  • not-tagged:ruby not-tagged:"ruby on rails"

not-state - Finds tickets not in the given state.


  • not-state:open
  • not-state:closed

Date-based Keywords

The updated and created keywords both use the same simple natural language parsing. Common examples can include:

  • updated:"5 days ago"
  • created:"7 months ago"

Modifiers like "before" or "since" can be added as well:

  • updated:"before 1 week ago"
  • created:"since 6 months ago"
  • updated:"since last monday"

You can use common english terms like days, months, years, etc. If you need something more exact, you can specify exact dates. Queries are parsed relative to the current date. However, this will search within the defined span.

  • updated:"Jan" - finds tickets from January 1 to January 31 of the current year.
  • updated:"January 2007" - finds tickets from January 1 to January 31 of the year 2007.
  • updated:"Jan 1 2007" - finds tickets from January 1 to January 2.

Other quick examples showing the flexibility of the date language:

  • updated:"5/27/1979"
  • updated:"27/5/1979"
  • updated:"05/06"
  • updated:"1979-05-27"

Sorting Results

  • sort:number - sorts results from lowest to highest ticket number.
  • sort:importance - sorts based on individual ticket importance.
  • sort:updated - sorts by previously updated tickets.
  • sort:milestone-importance - sorts by milestone then by importance then by updated.
  • sort:milestone - sorts by milestone, then by manual ordering within each milestone. So this sort works well when used along assigned:me or assigned:user as the manual ordering won't make sense for multiple users.