Great question. We put something in the FAQ for this:
In this first version of Jira Product Discovery, we’ve focused on some the jobs that help a PM do their job: prioritizing ideas and opportunities, creating and sharing roadmaps that stay up to date, and capturing feedback from a bunch of different places (interview notes in Confluence/Google Docs, conversations in Slack/Teams). But for now we assume the PMs have existing channels they use to receive feedback, and we help them send this feedback to ideas in Jira Product Discovery.
We have only partially tackled the job of creating a direct feedback channel between customers/users or other internal teams (sales/support/customer success/marketing) with the product team. We have plans to do more there, but for now these are the options that you can use to do that with the product today:
Set up a Jira Service Management queue to receive feedback from customers and internal teams
Set up a dedicated Slack channel #product-feedback to receive feedback from internal teams (also works with Teams)
Share views with other teams and gather their feedback using fields and votes to receive feedback from internal teams
Philosophically, "tickets" shouldn't be feature requests! Those are two different use cases, and it's dangerous doing what users ask for directly anyway, you know? :)
Here's an internal page we have on that topic, if you're interested.
We use JSM internally and externally, and ramping up Discovery separately for feature prioritization.
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events