You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
In looking at the Delivery feature. Are there plans to allowing the mapping/transferring of Idea metadata/field date to the delivery Epic/Story? As Product Management plans major initiatives, having that information (release name, target dates, etc.) passed/sync'd would reduce the time needed to keep information up to date. Optionally I am sure this could be handled via automation, as long as the "delivery" event can be trapped.
Hi @Ken Young , we are currently looking into the best way to improve the transition between discovery and delivery. Would you be open to chat about this - so we can understand your process? If so could you please book some time here?
My availability is limited next week, but you should find more time the week after that.
This goes for everyone who would like to help us design this. Thanks!
Just wondering if there has been any progress on this? It would be very helpful for our team to be able to map the metadata in discovery to specific fields on the delivery ticket.
Wondering if there's any follow up info on this? We require component in order to create issues. Without the ability to map fields between the tools or even specify required field values we cannot push issues from a discovery project to a software delivery project.
Hoping there's a clever way around this (or something planned) beyond linking back to product discovery after creating in a software project!
@Tony Urso we have someone working on improving the creation of Jira Software issues from Jira Product Discovery ideas at the moment - the first step there is: if we can't create the issue because there are required fields, it will open the Jira issue creation popup and pre-fill the summary (to let you do it in place).
Field mapping is not in the works yet - there are a few things that need to happen before that. HOWEVER, you could create automation rules (project settings > automation) to automatically fill some fields after the issue's created, if that helps.