Checklist for Spring Boot Configuration Completion Not Working
Check plugin status, version matching, file type, minimal projects, and cache/index issues in order.
When YAML or Properties completion does not appear in IntelliJ IDEA, check plugin status, file type, indexing, and project configuration in order.
First decide whether it is a plugin issue or a project issue
When completion does not work, do not reinstall immediately. First separate the scope. Create a minimal Spring Boot project. If completion works there, the plugin is basically functional and the issue is more likely related to file type recognition, indexing cache, or project import state in the current project.
If completion is missing even in the new project, check whether the plugin is enabled, whether the version matches your IDE, whether the IDE was restarted, and whether the package came from the correct version history entry.
Recommended troubleshooting order
Checking in order prevents wasted changes. In team environments, IDEA major versions, JDKs, and Maven/Gradle settings can differ across machines. Confirm local basics before investigating project-level causes.
- Confirm the plugin is installed and Enabled
- Confirm the plugin version matches the current IntelliJ IDEA major version
- Restart the IDE after installation or upgrade
- Confirm the file type is YAML, YML, or Properties
- Verify completion in a minimal Spring Boot project
- For existing projects, try reimporting or Invalidate Caches
When to switch plugin versions
If IntelliJ IDEA was upgraded to a new major version while the plugin was built against an older platform API, the plugin may install successfully but behave incorrectly. In that case, use the version history page to find a matching package instead of wiping IDE settings.
Typical signs of version mismatch include missing plugin actions, no completion in configuration files, or compatibility warnings in IDE logs.
Related guides
Independently maintained by ErickPang. Not affiliated with Spring, JetBrains, or Broadcom.