When using the 'Create delivery tickets' feature from the select menu, it would be great if there was some mapping options.
We can access the fields on the destination ticket.. why not allow us to auto populate from a field already completed in the idea?
Today, all that is copied over is the name of the idea.. not very useful.
This would reduce the need for automations.
We could select rows, create the delivery ticket, and do some basic mapping and done.
@Gavin Steele @Stephen_Lugton We're working on surfacing the idea info while you're looking at an Epic. A few pinned fields would be visible at first, and you'll be able to open the whole idea in a side panel. Would this do the job for you?
@Rohan Swami That's a good start, looking forward to seeing how the implementation works for us
I would be looking for this use-case as well.
For our workflow: We will use assignee's and a team that would represent the team in Jira discovery to filter ideas by team in views in jira discovery.
When we move to delivery, we also use two fields where we would want to carry over the team working on the feature as well as some other attributes of the feature.
Same use-case, ideally global fields would solve this, where we are staring to fill out the same fields that we use in jira discovery, will then carry over to Delivery.
Moving from product board, this will be a gap for us today, when pushing an idea from product board into jira allows you to populate specific fields in jira software so there is no duplicate entry when you get to jira.