IntelliJ IDEA 2025.3.1: Critical Fixes and the Rollback of Query Console

JetBrains rushed out IntelliJ IDEA 2025.3.1 just a week after the 2025.3 major release, fixing more than 200 reported problems and making a rare decision to roll back the experimental Query File feature.

SQL workflow rollback

The previous version tried to replace the long‑standing Query Console with Query File to treat queries like regular files. User feedback indicated severe regressions: global data sources became chaotic, familiar habits were broken, and multi‑project switching grew difficult. JetBrains publicly admitted the mistake and, to uphold a “zero‑regression” policy, restored the original Query Console without a patch.

What does this mean? In 2025.3.1 the familiar Query Console returns with its original behavior and default workflow.

If you have created Query Files recently, you have two options:

Delete them directly.

Recommended: Drag them into Scratches and Consoles | Database Consoles; they will be converted back to consoles.

Windows + WSL “lifeline”

Developers using WSL with Gradle on Windows encountered failures such as tests not starting, debugger time‑outs, and source‑code generation errors. All of these are listed as priority fixes in 2025.3.1, making the version a critical rescue for WSL users.

Gradle and Maven synchronization also became more reliable, especially for large, multi‑module projects that previously suffered mysterious sync failures, missing buttons, and incorrect root‑project detection.

Spring ecosystem fixes

Debugger: Bean evaluation failures and context‑loading errors during multi‑context tests are resolved.

Web development: The auto‑generation issue of Request Mapping is fixed; mixed properties and yml configurations no longer invalidate API version settings.

Kotlin + MongoDB: The missing gutter icon and broken completion for fields and JSON queries have been restored.

Java daily‑development experience improvements

Debugger stability: Groovy Step Into works again; the exception when stepping into

List

isEmpty()

is eliminated.

Reduced false positives: Red warnings for Optional.ofNullable() and unresolved AssertJ annotations are cleared.

Completion fixes: Auto‑completion after closing parentheses now works correctly.

Terminal and front‑end finally usable

Terminal: Long‑standing bugs such as path corruption, Backspace deleting the prompt, and Tab‑drag crashes have been fixed.

Front‑end: TypeScript upgraded to 5.9 with TSX generic false‑positive fixes; Vue multi‑script block completion and Nuxt path warnings are resolved.

Conclusion

Although only a week has passed, the speed of JetBrains’ response shows they are serious about correcting the aggressive changes in the previous release and polishing many experience details. If your IDE is still on 2025.3, open Toolbox or use Help → Check for Updates and upgrade to 2025.3.1 immediately.