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 narrow your submissions down to a specific set of results.
The following filter keys and possible values are available:
none, or any email of a User on the program
Matches on a User's email who has permissions on the program.
Matches based on whether the submission is a duplicate of another submission or not.
Matches if there is any payment on a submission.
Matches on submission state. Supports negative search.
-asc or -
desc depending on how you want it to be sorted.
Matches the severity assigned to the submission. Supports negative search.
Matches the origin of the submission. Supports negative search.
Matches on the target name. Supports negative search.
Matches the target type. Supports negative search.
Returns submissions based on the researcher's username who submitted them. Supports negative search.
< YYYY-MM-DD, or
Returns submissions that were submitted on, before, or after the date set.
Return submissions that have been awarded points or not
Return submissions that are currently blocked and need additional action from a specific user.
Matches the VRT category or subcategory.
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.
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.
Certain filters allow negative search, which allows you to find values that do not meet the specified value. You can think of a negative search like a blacklist. To perform a negative search, add a - before the key, like -state:triaged.
You can perform a negative search with the following filter keys: state, program, and target.
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.
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.
The tokenized search bar allows for multiple sorting criteria. Sorting parameters will be applied to search results in the order they are declared in tokens. Below an example sorted first by priority and second by old to new:
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:
Finds new submissions that need to be reviewed.
Returns submissions that have been triaged and need to be accepted or rejected.
Shows submissions that are valid and need to be resolved.
Looks for submissions that have been fixed and may need to be retested by the researcher.