On this page


Search works across all the DevRev apps to provide you with smooth navigation and access to issues, tickets, articles, customers, and more. Using search queries and commands helps you filter and give you more accurate search results.

To initiate the search you can do Cmd + K on Mac or Ctrl + K on Windows or click Search on top of the left navbar.

A search query consists of the following syntax:

1 [operator]* [field]* [term/phrase]*

The above query specifies the following:

  • Filtering
  • Full-text search terms/phrases

Filtering is denoted by the query's [operator]* [field]*, which represents a logical AND of all operators (if specified). This is used to reduce the list of possible objects that can be returned in search results.

Full-text search terms/phrases are denoted by [term/phrase]* and are used to do full-text searches on object text fields.

Example: state: open, closed (field value)


Operators are used to filter the search results. The following table shows the syntax of each operator along with examples.

in:<body/title>Aids in searching within the body of the ticket/issue/enhancement or title.in: title crm
in: title "crm exp"
in: title crm exp
in:body "bot issues"
type:<object type>Enables users to filter by object type. Supported object types include: issue, enhancement, ticket, revu (for searching contacts), question_answer, conversation, article, devu (for searching dev contacts), account, feature, runnable.type:issue
type:enhancement in:title CRM
type:enhancement, opportunity
type:issue, enhancement in:title crm
-Acts as an exclusion in search results. "-" can be used for the same purpose.type:issue - crm
type:issue in:title - crm
stateFilters results based on the stage: open, closed, or in_progress.state:open
severityFilters out tickets with the desired severity level. Supports: blocker, high, medium, low.severity:high
type:ticket -severity:low (filters all tickets excluding the ones with low severity)


Fields can be used along with operators to filter the search results further. The following table shows types of fields, syntax and it's examples.

Types of fieldSyntaxExamples
Fields<field_name>:true (or :1)
<field_name>:false (or :0)
isCustomer: True
Submitted: 0
Numeric fields<field_name>:<v>, <field_name>:<<v>, <field_name>:><v>
revenue: < 100
revenue: 500..2000
tickets=< 5
String fields<field_name>:<v>Name: alice
Name: Alice,bob,eve
Date fields<field_name>:<v>
target_release_date< 2020-10
target_release_date< 2020
Array fields<field_name>:<v> Here <v> is a CSV list of values where a match occurs if the array field contains an element having any of the values in the list.tags: performance (string array)
magic_dates_c: 1970-01-01,2006-01-02 (date array)
Modified_date: 2024-01-02..2024-01-05 (fetches records that were modified between 2024-01-02 and 2024-01-05)
created_date: 2023 (fetches records that were created in 2023)