As part of the issue management process, you analyze each detected issue and assign it a status that indicates how it should be handled. We call this process "citing".
Note: Users require permission to change an issue's status. Permission can be granted to change from or to any status or only for specific statuses. For example, a group of users may only have permission to change issues in "Analyze" status to "Fix".
|Status||Use this status to indicate that the issue...|
|Analyze||should be reviewed (default initial status). All newly detected issues display this status. It persists until you change it.|
|Ignore||intended for issues found (whether valid or otherwise) in code you don't care about, for example test code|
|Not a problem||false positive; the issue reported isn't valid. Relates to an analysis failure, and is often caused by build integration problems. Klocwork recommends opening a Customer Support Request (CSR) when you determine that a reported issue is a false positive, so that we can analyze the issue and make improvements to the engine, if necessary.|
|Fix||a valid issue that should be fixed as soon as possible|
|Fix in Next Release||a valid issue that is mostly harmless and can be left in the code base without too much risk, but should be addressed sooner rather than later|
|Fix in Later Release||a valid issue that is completely harmless and can be left in the code base indefinitely without risk|
|Defer||a valid issue that needs discussion with others or escalation to (for example) a security team for final judgment|
|Filter||provided for compatibility with older versions of Klocwork filter files|