How do you update the JPD fields in automation?

Question

We are trying to implement a JSM form to capture new idea requests from any of our JSM customers. We want to had a standard look and feel and make it one stop for our employees for submitting requests, incidents, etc. We are creating automation to move the data from the JSM form to the JPD idea. Is there a way with automation to access the JPD fields? We haven't found a way to update the JPD fields so created custom fields to duplicate the capture of the information which is not what we want to do.

I posted the question below because we are trying to figure out how allow our JSM customers to submit ideas. A response was automation between JSM form and JPD. We also found that we could add all the JSM customers to the contributor role yet that seems like more administrative overhead to allow our employees to submit ideas.

https://community.atlassian.com/t5/Jira-questions/Is-a-Jira-or-JSM-License-required-to-submit-an-idea-with-Jira/qaq-p/2738514

Joni Johnson · Answer

Hello @Nick Haller

My apologies for including the text in the response above that we are capturing the initial request in JSM and create the JPD item. We are creating the link to JPD just like the video and trying to do updates between the JSM ticket and the JPD idea and vice-versa. We haven't found a way from our JSM project that captures the questions to update the JPD project specific field with the answers.

I'll take a look at what you shared. We have one JPD Intake project that we want all ideas submitted from JSM to capture. We want to use the JPD project specific fields since they are only used in this JPD project.

Thank you.

Nick Haller · Answer

Hi @Joni Johnson ,

Apologies. I thought the workflow was JSM >> JPD, but it sounds like it's the other way around for JPD >> JSM.

This should still be possible. I wrote an article recently that should help share some insight into how this is possible:

Mapping JPD idea fields → Jira delivery fields using automations

Although that article touches upon mapping the idea's (JPD) fields to the delivery's (Jira) fields, the idea would be the same.

Instead in the WHEN condition of selecting the Polaris issue link, you would want to select the link-type you are using to link the JSM issue to the JPD idea.

For example if the link-type "relates" you could use that in the WHEN condition. Might look something like this:

Whatever field you are mapping to (JSM), you would be copying the JPD field which is the Destination issue:

Joni Johnson · Answer

Hello @Nick Haller

While this video gives great tips on the automation between JSM and JPD, it does not address the question I was attempting to ask. We have an Intake Project that has the JPD project specific fields. We are creating the JPD issue and linking it to the JSM item with a relationship.  We want to create the JPD intake issue and set the JPD project fields for the JPD Intake Projects and not setup global fields. Is there a way to access through automation the JPD specific project fields to update from JSM to JPD?