@NotNull field is not initialized

Reports fields annotated as not-null that are not initialized in the constructor.

Example:

public class MyClass {
  private @NotNull String value;

  public void setValue(@NotNull String value) {
    this.value = value;
  }

  public @NotNull String getValue() {
    return value;
  }
}

Such fields may violate the not-null constraint. In the example above, the setValue parameter is annotated as not-null, but getValue may return null if the setter was not called.

Locating this inspection

By ID

Can be used to locate inspection in e.g. Qodana configuration files, where you can quickly enable or disable it, or adjust its settings.

NotNullFieldNotInitialized

Via Settings dialog

Path to the inspection settings via IntelliJ Platform IDE Settings dialog, when you need to adjust inspection settings directly from your IDE.

Inspection ID: NotNullFieldNotInitialized

Inspection options

Here you can find the description of settings available for the @NotNull field is not initialized inspection, and the reference of their default values.

Ignore fields which could be initialized implicitly

Option ID:

IGNORE_IMPLICITLY_WRITTEN_FIELDS

Default value:

Selected

Ignore fields initialized in setUp() method

Option ID:

IGNORE_FIELDS_WRITTEN_IN_SETUP

Default value:

Selected

Suppressing Inspection

You can suppress this inspection by placing the following comment marker before the code fragment where you no longer want messages from this inspection to appear:

//noinspection NotNullFieldNotInitialized

More detailed instructions as well as other ways and options that you have can be found in the product documentation:

IntelliJ IDEA 2025.3

Inspection Details
By default bundled with:	IntelliJ IDEA 2025.3, Qodana for JVM 2025.3,

Last modified: 03 December 2025