User Guide
Chapter 3: Using the Fortify Remediation Plugin
tree. After you type a search term, the label next to the folder name changes to indicate the number
of issues that match the search as a subset of the total. For example, Hot (2 of 5).
To indicate the type of comparison to perform, wrap search terms with delimiters. The following table
describes the syntax to use for the search string.
Comparison
contains
equals
Description
Searches for a term without any special qualifying delimiters
Searches for an exact match when you enclose the term in quotation marks ("")
number range Searches for a range of numbers using the standard mathematical interval
notation of parentheses and/or brackets to indicate whether the endpoints are
excluded or included respectively
Example: (2,4] indicates greater than two and less than or equal to four
not equal
Excludes issues specified by the string when you precede the string with the
exclamation character (!)
Example: file:!Main.java returns all issues that are not in Main.java
You can further qualify search terms with modifiers. The syntax to use for a modifier is
modifier:<search_term>.
If you specify more than one modifier, the search returns only issues that match all the modified
search terms. For example, file:ApplicationContext.java category:SQL Injection returns
only SQL injection issues found in ApplicationContext.java.
If you use the same modifier more than once in a search string, then the search terms qualified by
those modifiers are treated as an OR comparison. For example, file:ApplicationContext.java
category:SQL Injection category:Cross-Site Scripting returns SQL injection issues and
cross-site scripting issues found in ApplicationContext.java.
For complex searches, you can also insert the AND or the OR keyword between your search queries.
Note that AND and OR operations have the same priority in searches.
Search Modifiers
You can use a search modifier to specify to which attribute of an issue the search term applies. To use
a modifier that contains a space in the name, such as the name of the custom tag, you must enclose
the modifier in brackets. For example, to search for issues that are new, type [issue age]:new.
A search that is not qualified by a modifier tries to match the search string on the following issue
attributes: kingdom, primary rule id, analyzer, filename, severity, class name, function name, instance
id, package, confidence, type, subtype, taint flags, category, sink, and source. For example:
l
To apply the search to all modifiers, type a string such as control flow. This searches all the
modifiers and returns any result that contains the specified string.
Micro Focus Fortify Plugins for JetBrains IDEs and Android Studio (22.1.0)
Page 42 of 56