When the gap is mostly a known limit question
Start with known-limits interpretation when the real question is whether the current boundary is expected, acceptable, or still compatible with your trial or migration decision.
This is different from assuming the product is broken or assuming the gap is already a roadmap promise waiting to be activated later.
When the gap belongs somewhere else
Use support when the next step is blocked or consequence-heavy, bug reporting when the current experience appears broken relative to the intended path, and feature request when the missing capability matters but the product is not actually malfunctioning.
The safest first route is the one that preserves the real signal without forcing more certainty than you actually have yet.