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.
Thx
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?
https://calendly.com/tcrusson/30min-1
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!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello,
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey there,
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!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
hey , is there is any updates regarding this feature , because right now we still don't have this feature and we cant change project custom fields to be global fields to use in multiple project
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.