Use to filter by status, severity, owner, or checker code.

To show only local issues, toggle Show local issues only (relevant only for connected projects).

Group issues by module, package file, issue type or severity.

Filter settings remain in effect for this project until you change them again, even if you close and reopen IntelliJ IDEA.

On the Klocwork for Java Project Settings page, you can:

• Connect to a Klocwork Server project
• Enable and disable checkers (click Edit; see "Enable and disable checkers" below)
• Import, export or delete:

  a user profile (.pconf)

  a metrics configuration file (.mconf)

  one or more knowledge bases (.jkb)

• Edit a knowledge base file
• Specify which modules in your project should be analyzed, if your project contains more than one module.
  Tip: The analysis button in the toolbar always analyzes modules that you've selected on the Klocwork for Java Project Settings page. By contrast, using the right-click Run Klocwork for Java analysis menu option analyzes modules that are currently selected in the Project Explorer (whether or not they are selected on the Project Settings page).
• Disable parallel analysis

Typically, server information is set during installation. However, when this information changes, you need to update it. On the Klocwork for Java IDE Settings page, you can:

• Set the host and port information for the Klocwork Server.
• Specify a secure connection to the Klocwork Server.
• Specify the host and port information for the License Server.

You enable and disable checkers in the Configuration Editor. This task requires permission to change your local configuration.

To enable or disable checkers:

1. Go to File > Settings, then under Other Settings or Project Settings (depending on your version), select Klocwork Static Analysis.
   Note: The Klocwork Static Analysis panel is not visible until your project is configured and/or the issues are synched.
2. Under Configuration files section, right-click on a profile (the default one is called 'Analysis profile') and click Edit.
3. Select and deselect checkers as required. To learn more about the checkers, see the Java checker reference.
4. Use the Search field to locate checkers by code, title, reference, category or taxonomy. Your changes take effect when the next analysis is triggered.
   CAUTION:
   Clicking Restore Defaults restores all factory default settings.
5. Once you are finished making changes, click OK to finalize the changes.

For connected desktops, you may need to investigate or fix a system issue. Klocwork Static Code Analysis provides a System ID for each detected issue. By default, the connected desktop does not identify issues by System ID in the issue list.

To locate a system issue:

1. Obtain as much information about the issue as you can, such as the file in which the issue is located, issue type (ABR, for example), line number, owner (if applicable) and severity.
2. Make sure the "Show Local issues only" setting is toggled off.
3. If you know what module the issue is in, as well as the file name and issue type, then group by module, file and issue type. In the Klocwork for Java view, make sure the following grouping controls are selected:

   Module

   File

   Issue type

4. View the contents of the Issue type group to find the right system issue.

You can view the status and comment history for selected issues in the Klocwork for Java view.

Right-click an issue in the Klocwork for Java view and select Status history.

The Status History dialog displays the history of issues detected in a connected desktop project. The name of the user who made the changes and the date and time of the edits are included. The date and time of the initial status of Analyze are always noted first.

If you are connected to a server project but synchronization is disabled and you have not yet synchronized manually, or your project is in standalone mode, only your latest status change is displayed.