How to create delivery ticket along with all/selected fields?

Question

So I've been trying JPD and so far it helps a lot narrow down the priority ideas.

During the brainstorm, I use "Impact score" and I may add some custom fields to categorize the ideas, let's say it's "Product".

However, when I already have some ideas that is ready to be pushed to Jira Software, I found that the only auto-filled field is "Summary". How about "Impact score" or "Product" field that I spent many hours to categorize and do the weighting ?

It's weird that from JPD -> Jira Software the Idea/Issue informations are disconnected. And the only way I can retrieve is to click the linked idea, which redirects to another page.

I've tried automations but it doesn't seem support automation between 2 worlds: JPD & Jira Software.

So far, my solution is to create custom field in Jira Software and marks it as "required", so that when I create a delivery ticket from JPD, I need to manually "re-define" the field with the existing value in JPD.

Please your guidance.
Thanks

Rohan Swami · Answer

Hi @Arnold we're working on some solutions to this problem at the moment. Would you like to book a Zoom call with me on Calendly so that we can incorporate your feedback in our solution?

Hermance NDounga · Answer

As Alevia mentions, it's possible to do it, as long as your fields are not unsupported type (formula, vote view full list here) .

We also released some templates so i suggest to use :

* When delivery ticket is created → Copy description from idea"

and tweak it according to what needs to be copied over.

Alevia Thomson · Answer

Automation for Jira absolutely supports pushing information from JPD ideas to Jira Software issues. This is a good place to start: https://support.atlassian.com/jira-product-discovery/docs/automate-actions-in-the-delivery-panel/

Some key tips:

* use the link type “implements” as a condition to narrow the search down and/or
* use an advanced compare condition to confirm the destination issue type is an idea
* take note of the date field advice further down on the above link, it’s far more complicated than would be expected!