Welcome to Bugcrowd's Product Documentation Center

You'll find comprehensive guides and documentation to help you start working with Bugcrowd as quickly as possible.

Filtering Submissions

You can use filters to view submissions that match a particular set of criteria. For example, you can query submissions that you may need to follow up on, such as ones that still need to be reviewed or fixed.

To filter your submissions, you create a query using filter keys.

Filter Keys

Filter keys narrow your submissions down to a specific set of results.

The following filter keys and possible values are available:

Key
Value
Notes

assignee

me, none, or any email of a User on the program

Matches on a User's email who has permissions on the program.

payments

none or present

Matches if there is any payment on a submission.

state

new, triaged, wont-fix, not-applicable, out-of-scope, unresolved, and resolved

Matches on submission state.

sort

payment, points, severity, submitted, or updated

Appends -asc or -desc depending on how you want it to be sorted.

severity

1-5, none, or present

Matches the severity assigned to the submission.

source

api, csv, external_form, platform, or qualys

Matches the origin of the submission.

target

Matches on the target name.

target-type

android, api, hardware, ios, iot, other, or website

Matches the target type.

researcher

Returns submissions based on the researcher's username who submitted them.

Filter Syntax

To create a query, you need to use the following syntax: <filter key>:<value>. Make sure you include a colon after the filter key and do not include any spaces between the filter key and value.

You can enter multiple filter key/value pairs in the query, such as: state:unresolved severity:1. By default, the query includes sort:submitted-desc, which sorts your submissions in descending order based on the dates they were submitted. You can remove or replace this filter key/value.

Filter Logic

There is an AND operator between unique filter keys; however, multiple instances of the same filter key use the OR operator. For example, state:unresolved severity:1 returns all P1 submissions that have been triaged but have not been fixed. The query state:unresolved severity:1 severity:2 returns all P1 and P2 submissions that have been triaged but have not fixed.

Building a Query

To help you build a submissions query, a list of available filter keys will appear when you click in the search field. After you select a filter key, the search field will show you possible values based on what you've selected.

Remember, you can use as many key/value combinations you need, and there is an AND operator between unique filter keys and an OR operator between multiple instances of the same filter key. As you add filter key/value pairs to the query, the results automatically refresh to show you the latest results.

Note

If you input an invalid filter key or query, no submissions will be returned. Please review your queries for any errors if the results do not show the submissions you expect to see.

Preset Queries

There are preset queries available that let you quickly find submissions that are new, need to be reviewed, need to be fixed, or have been fixed. Just click on the filter and the query will display in the search field.

The following preset queries are available:

Query
Filters
Description

Processing

state:new

Finds new submissions that need to be reviewed.

To Review

state:triaged

Returns submissions that have been triaged and need to be accepted or rejected.

To Fix

state:unresolved

Shows submissions that are valid and need to be resolved.

Fixed

state:resolved

Looks for submissions that have been fixed and may need to be retested by the researcher.

Filtering Submissions