Why IntelliJ IDEA 2025.3.1’s ‘Rollback’ Fix Is a Game‑Changer for Java Developers

JetBrains released IntelliJ IDEA 2025.3.1 just a week after the major 2025.3 version, addressing more than 200 issues and reversing a risky change to the database query workflow.

SQL workflow rollback

The previous release introduced Query File to replace the long‑standing Query Console. Users reported severe regressions—global data sources broke, habits were disrupted, and multi‑project switching became painful. JetBrains publicly admitted the mistake and rolled back to the original Query Console without a patch.

What does this mean? The familiar Query Console returns in 2025.3.1 with its original behavior.

Created a Query File? Either delete it or drag it to Scratches and Consoles | Database Consoles to restore the console.

Windows + WSL “lifeline”

For developers using WSL + Gradle on Windows, the new version fixes three major pain points:

Tests that wouldn’t start.

Debugger connection timeouts.

Source‑code generation failures.

These issues are marked as “key fixes,” effectively rescuing the WSL development workflow.

Spring ecosystem fixes

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

Web development: Request Mapping auto‑generation works again; mixed properties / yml API version settings no longer break.

Kotlin + MongoDB: Icons, field completion, and JSON query suggestions are restored.

Java daily‑development experience improvements

Debugger stability: Fixed Groovy Step Into issues and List.isEmpty() exceptions.

Reduced false‑positives: No more warnings for Optional.ofNullable() or AssertJ annotations.

Completion fixes: Bracket‑closure completion works again.

Terminal and frontend updates

Terminal: Path handling, Backspace behavior, and tab dragging bugs are fixed.

Frontend: TypeScript upgraded to 5.9, fixing TSX generic false‑positives; Vue multi‑script block completion and Nuxt path warnings are resolved.

Conclusion

Although released only a week after 2025.3, version 2025.3.1 demonstrates JetBrains’ rapid response to community feedback, undoing a disruptive change and delivering a broad set of stability and usability fixes across Java, Spring, SQL, WSL, and frontend tooling. Users still on 2025.3 should update immediately via Toolbox or Help → Check for Updates.