The ticket system features a powerful and sophisticated search which allows you to search tickets generally or based on specific attributes. The guide below shows the options available to you when searching.
It's useful to remember you combine any of the options below to create a more powerful query.
Searching Summaries
To search a summary, you just need to enter what you're looking for. If you're looking for all tickets about
installation you can simply enter installation into the search field.
Filtering Results
Searching IDs
To search for tickets with a specific ID (or set of IDs) you can run any of the following:
id:5will return ticket #5id:1,2,3will return tickets #1, #2 and #3
Of course, if you know the ticket ID you can enter the direct URL to the ticket into your address bar using
http://dave.codebasehq.com/widgets/ticket/1234 for ticket 1234. If the ticket isn't found, you will receive a page not found message.
Searching based on properties such as status or priority
status:new,acceptedwill return all tickets with the new or accepted status.priority:highwill return all tickets with the high prioritycategory:cosmetic,apiwill return all tickets in the cosmetic or api categoriestype:bugwill return all bugs. You can also useenhancementortask.
If you have a property which contains a space, you should encapsulate it with double quote marks.
status:"In Progress"will return all tickets with the in progress status.status:"In Progress",newwill return all tickets with the in progress or new status.
Searching for open and closed tickets
If you'd prefer to search based on status type (i.e. whether or not the status is considered open or not) you can use the following:
status:opento return all tickets with an open statusstatus:closedto return all tickets with a closed status
Inverse Searching
To search for the opposite of an attribute, you can prefix
not- to the attribute name.
not-status:newreturn all tickets which do not have the new statusnot-priority:lowreturn all tickets which are not considered low priority
Actor/User Searching
If you'd like to search for tickets using their assignment or reporter attributes you should simply use their username as the search value.
assignee:adamreturn all tickets assigned to adam.reporter:jack,charliereturn all tickets reported by jack and charlie.
If you are looking for tickets assigned or reported by yourself, you can use the
me keyword. This keyword is especially useful when creating searches which will be saved for other to use.
assignee:mereturn all tickets assigned to you/currently logged in userreporter:mereturn all tickets reported by you/currently logged in user
Searching for any or none
If you're looking to search for all tickets which aren't currently assigned a user or all tickets which do have a milestone you can use the
all and none keywords to your advantage.
assignee:nonewill return all tickets without a currently assigned usermilestone:nonewill return all tickets without a milestoneassignee:anywill return all tickets which are assigned to somebodymilestone:anywill return all tickets which do have a milestone
Sorting Records
You can order & sort the results you receive from a search using the
sort and order operators. By default, we order by priority but you can change these using the options below
sort:id order:descwill order by the ticket ID descendingsort:priority order:ascwill order by priority with the most important at the top (ascending).
Example Queries
The queries below may prove useful:
assignee:me status:openreturn all my open ticketsstatus:open milestone:nonereturn all open tickets without a milestonestatus:open assignee:me not-priority:lowreturn all my open tickets which are not low priority