I'm used to issues being the entries on the user-facing interactions (support tickets), and if some further project action is necessary, they're linked to in a task and taken onto the Kanban board and planned into sprints. More often, the support just answers a question and closes the support ticket.

That's how we use issues in #GitCitadel, as well.