Using an issue-tracking tool to collect feedback is like trying to use a hammer for a screw. It's not that it can't be done, but it's certainly inefficient.
Let's take a real-life example your team surely experienced before:
A customer success manager hops off a call with a user and sends a Slack message in the #product-feedback channel with a bullet list of 2 bug reports, 3 feature requests, 1 kudo, and 2 overarching problems.
How do you act upon that feedback?
This is where issue trackers fall short.
They simply don't have the right data model for this use case.
Wrote this article on how to fix this.
