User interface overview

Actual problems

Using this tab, you can overview the problems found during the current Qodana run.

This includes several elements:

1. The sunburst diagram provides a graphical overview for the problems and allows you to drill down into the cause of the issue.

2. The filter lets you filter the report data.

3. Configured filters can be saved using the Save as... button. The Reorder button toggles the editing mode, so you can rearrange the sunburst diagram by dragging its components.

4. The Problems tab lists and classifies all detected problems by severity, filename, path, category, and type. The Files tab presents problems in the file tree.

5. The Move to baseline button saves the selected problems to the Baseline list.

6. Clicking a problem in the list will expand the underlying code fragment to provide the detailed description.

7. If you have JetBrains Toolbox and Qodana IDE plugin installed, you can edit the file containing the problem using your IDE. To do it, select your IDE from the dropdown list, and click the Open file in button.

   

   Gif

   If you have several versions of the same IDE, you can select which version will be used to open the file. In the JetBrains Toolbox UI, drag or move the required version of the IDE to the top of the list using the Ctrl + Shift + ↑/↓ shortcut on Windows or Linux, or ⌘ + ⇧ + ↑/↓ on macOS.

   The More actions list provides other options for handling problems, see the Adjust the analysis scope section.

Baseline

When you click the Move to baseline button in the Actual problems tab, the selected problems will move to this tab.

This tab structure is similar to the Actual problems tab. To enable the baseline feature in future runs of Qodana, download the configuration file and save it to the project root folder. For more information, explore the Baseline section.

Checks

The Checks tab lists the inspections and lets you adjust your inspection profile by specifying a set of inspections that Qodana will be using during next run.

Here, you can study each inspection, enable or disable it. To use this configuration for future Qodana runs, you can download the qodana.yaml file in the Profile configuration section, and save it into your project root directory.

See the Adjust your inspection profile section to learn the best practices.

tip

To learn more about inspection profiles, see the Set up a profile section. You can also edit profile settings in the qodana.yaml file.

Project audit

The Project audit tab contains results of inspection by the License audit feature.

This tab contains several other tabs:

• Languages enumerates all technologies currently supported by Qodana

• Translators lists all technologies that were involved for inspecting the codebase

• Project License contains information about the license used in the project

• Third-party licenses lists all project dependencies and the licenses they use including dependencies that cannot be used under the current project license.

  

  If you want to filter the list by dependencies that cannot be used under the current project license, you can enable the Only alerted switch.

  

• License rules contains the table of license compatibility.

  

  The Project license column lists license names, while the Allowed licenses and the Prohibited licenses columns list the licenses that are compatible and incompatible with the license respectively. This can be helpful when you need to override licenses.

Reduce the scope of analyzed issues

When viewing a code fragment with a detected problem, you may decide that it is irrelevant. You can make sure that more problems of the same type are omitted in the future. For this purpose, you can edit qodana.yaml or use the Problem and File explorers in the UI as shown below.

1. Exclude a file or directory from the future analysis

Reason: The analysis of the file containing the error, or even the directory containing this file, doesn't make sense in your project. For example, it's actually not the source code but some generated or downloaded content.

Howto: Under the code fragment view, click More actions and select the necessary option.

OR:

Above the code fragment view, click the file path to navigate to the File explorer.

You can mark the file/directory as Excluded.

2. Hide a problem type or category from the list of problems

Reason: You suppose that the type of the error or its category is not relevant or want to get back to it later.
Howto: Under the code fragment view, click More actions and select the necessary option.

tip

If you exclude either type/category or file/directory, the UI will remind you to save the changes if you want to use them in future checks. Download the qodana.yaml file and store it under your project root directory.

Enable excluded or hidden problems

To reverse the exclusions you made, download qodana.yaml in the Profile configuration section, edit it as necessary, put it in the project root directory, and then run Qodana again with this new configuration.

To learn how to configure Qodana using qodana.yaml, see the Configure profile section.