Intellij Ultimate中「Creates missing switch branches」意图功能无法使用的问题求助

I’ve run into this exact frustrating issue before—here are some practical, tested steps to troubleshoot and fix it:

• Verify your code meets the trigger criteria
  This intention only works for specific types: enums, sealed classes (Java 17+), or types with a fixed set of constants. If you’re using a plain int/String without existing branches, it won’t trigger. Also, make sure your cursor is placed directly on the switch keyword or the switch variable—not elsewhere in the block.

• Double-check inspection and intention settings
  It’s not enough to just toggle the feature on/off:

  1. Go to Settings > Editor > Inspections > Java > Control flow issues
  2. Ensure "Switch statement without all branches" is enabled (this is the inspection that triggers the quick fix)
  3. Then head to Settings > Editor > Intentions > Java > Control flow
  4. Confirm "Create missing switch branches" is checked

• Rule out shortcut conflicts
  Alt+Enter might be hijacked by another plugin or system shortcut. To test:

  • Press Ctrl+Shift+A (Windows/Linux) or Cmd+Shift+A (Mac)
  • Search for Show Intention Actions and run it directly
    If the intention menu pops up (with the missing branches option), your Alt+Enter is conflicting. Fix it in Settings > Keymap by reassigning the Show Intention Actions shortcut.

• Invalidate caches and restart
  Don’t skip this—corrupted cache is a common culprit for weird IntelliJ glitches. Go to File > Invalidate Caches..., select Invalidate and Restart, and let the IDE rebuild everything from scratch.

• Test in Safe Mode
  Third-party plugins can interfere with native IDE features. Start IntelliJ while holding the Shift key to enter Safe Mode (all non-bundled plugins disabled). If the feature works here, enable your plugins one by one to find the problematic one.

• Check for version-specific bugs
  Sometimes the latest "stable" version has unforeseen issues. If all else fails, search for the problem in IntelliJ’s issue tracker, or roll back to the previous minor stable version (e.g., from 2024.2 to 2024.1.1) to see if that resolves it.

内容的提问来源于stack exchange，提问作者BarbetNL