How do I decide if something is a bug or a feature request?

The core distinction
If the current behavior doesn't match documented or intended behavior, it's a bug. If the current behavior is working as designed but you want something different, it's a feature request.
Example: If the app *should* show a confirmation dialog when deleting data but doesn't, that's a bug. If you want a confirmation dialog where none was specified, that's a feature request.
Gray area test
When in doubt, ask: "Is this breaking an existing promise to users?" If the documentation says it should work a certain way and it doesn't, it's a bug. If the documentation is silent, it's likely a feature request.
Why this matters
Developers prioritize bugs over features. Misclassifying a feature request as a bug clogs the critical backlog and wastes time. Misclassifying a bug as a feature request lets serious problems sit.
Set a team standard
Decide this once as a team, document it, and stick to it. Consistency prevents endless arguments about categorization.