Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

How do you manage feedback intake & triage in JPD?

David Nadri
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
August 1, 2025

TLDR: What are some effective ways your team actually uses to intake and triage feedback in JPD — beyond the common approaches already covered in JPD’s FAQs (e.g. custom fields, separate projects, Slack/JSM intake, etc.)?

Ideally, the best approach should let teams (CSMs, Sales, etc) (1) easily check if an idea already exists, (2) add new ideas or insights when needed, (3) and avoid cluttering core JPD views for the product team. How have you tackled that?

 

Hello JPD Community! 

We’re setting up a simple, scalable way to collect and triage product feedback (from CSMs, Support, etc.) in Jira Product Discovery — all in one JPD project.

We’ve already explored the usual suggestions in the JPD FAQs (separate intake project, JSM queues, Slack/Teams channels, custom “triaged?” field, etc.) — but they come with trade-offs like fragmented views or extra overhead to maintain filters.

I know the JPD team is exploring improvements to insights, feedback, & intake on their roadmap (JPR-16), but I’d love to hear how folks are handling this today using existing JPD features. Looking for:

  • Real-world setups that work for your team

  • How you collect, review, and prioritize insights

  • How you avoid flooding views with untriaged ideas

  • Examples of views (& how they're configured) or workflows that work well

Any tips, lessons, or screenshots would be super helpful. Thanks!

0 answers

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events