Jira Product Discovery to Software project handoff - what fields are you syncing in 2026

[HEMANT SAINI]

JPD is pushing more dev handoff features now. We want Ideas to auto create Epics in JSW with custom fields mapped. The native link works, but we lose votes and insights. Are you using Automation, Forge, or the native integration. How do you keep discovery data visible after it becomes a delivery issue. Would love to see field mapping examples.

[Tomislav Tobijas · Accepted solution]

Hi @HEMANT SAINI ,

I'd say it depends on which data you'd like to see in the software area, but mainly we're talking about Jira automation (that's how we implemented projects, at least). Mostly, votes and such are left in JPD, and there's always a link from Epic to the Idea that generated it, so users can see additional context that may not be available on the Epic/software work item itself. 👀
We didn't do actual mapping of votes and insights, but maybe someone else who actually did this will chime in.

But, if you'd like to see those values on the software side, I believe automation will/should be able to handle conversions from JPD fields to classic Jira fields. ⚙️

I do know (and this is a cool thing) that customers tend to use JPD and Jira Plans combined. There's a solid article on how you can combine the two: Jira Product Discovery and Jira Plans 

Hope this helps.

Cheers,
Tobi