Directional Thoughts on Insights, Feedback and Intake?

[Stacey Steiger]

Hi there, 

Context: I am a new product leader coming into an organization that is overloaded with aligning with internal teams. I am an extensive JIRA user, but JPD is new to me. I have previously used other tools for product-centric work that integrated into JIRA. Those products were quite sophisticated in feedback intake and management where (per your acknowledgment JPD is not yet)

Before I arrived my team started using JPD and I see many benefits, but since my current priority is internal alignment, I am trying to decide if I can make JPD work while you all are exploring the area I need most. 

Having read and watched as much as I can find, and reviewed the handbook, I feel like your recommended approach is to intake feature request via a JSM project which my company doesn't use. I also see some recommendations to dedicate a project specific to intake.

However, in recent looms related to the hierarchies feature, and with the future addition of intake forms per type, I begin to feel like you might be envisioning a concept that feature requests are an early type of idea and perhaps that early idea in the future may then become an insight attached to a larger item.  I know this is still in exploration and the acquisition of cycle may influence, but I am wondering if you have directional thoughts at this point? 

[Tanguy Crusson · Accepted solution]

Hi @Stacey Steiger you are right, we've been kind of playing 3D chess on all this 😅

We're currently working with the Cycle team on envisioning what the future looks like for feedback and intake, and how that integrates with the rest of JPD (including hierarchies). And that's based on everything we've learnt when building Cycle and JPD over the past few years. 

We'll share back when we get somewhere, and to get feedback from the community. But needless to say we're going to overhaul this area and finally give it the attention it deserves. 

[Olha Yevdokymova_SaaSJet]

Hi @Stacey Steiger 
Welcome to JPD and thanks for the thoughtful breakdown - you’ve nailed one of the biggest gaps many teams feel when getting started: structured intake.

You’re right that Atlassian’s current guidance leans on JSM intake or dedicated projects, but if neither fits your setup, another path you might explore is Smart Forms for Jira (developed by my team). It gives you a way to capture requests through flexible forms and then map those responses directly into JPD as new ideas.

Here’s how that works in practice:

• Intake anywhere: You can share forms externally (link, embed on Confluence or your site) or use them internally in issues in different projects. This helps you unify all feedback sources without giving everyone access to Jira.

• Configure the form to create a JPD idea automatically in a you Jira Product discovery project.

• Field mapping: Each form response can be mapped to JPD fields (summary, description, custom fields, tags, etc.), so when someone submits, a properly structured JPD idea is created automatically

• Traceability: Because form submissions stay linked, you can always trace a JPD idea back to the original requestor or context, which helps when you’re aggregating similar asks into insights.
• Since the form does the intake work, you only need one JPD contributor. No need to buy additional contributor seats just to allow stakeholders to submit requests.

Happy to share a step-by-step setup if you’d like to see what that form → idea mapping looks like.