Flow Designer > Jira Spoke 2.6.5 > Update Issue > Additional Fields "Add Field Value" is grey out?

jasonthorngren · ‎04-22-2020

Is this expected? Or should I be able to add field values to other Jira Issue fields?

Any info is appreciated... Thanks!!

Michael Fortson · ‎10-22-2020

Here's a much simpler trick for setting Issue field values (priority etc) in Jira, working around the problem posted above. Follow these steps carefully.

- Initially set up the Update Issue action with hardcoded issue ID & field value -- this will let the action fetch the properties and fields
- SAVE your flow/subflow
- Hit the Script button on your Field value, and change that value to use your input variable or previous step value via script (e.g. return fd_data.subflow_inputs.priority)
- Save
- Change issue ID to use input via script (see above)
- Save

Done!

View solution in original post

Dennis38 · ‎06-03-2020

Hello,

I was having this issue yesterday and the following KB helped me.

https://hi.service-now.com/kb_view.do?sysparm_article=KB0818189 Title is .. Additional Fields are greyed out when you configure Issue ID with a pill in "Update Issue" action in Flow Designer for Jira Spoke.

Thanks!

Vladimir6 · ‎08-07-2020

Dennis, you saved my day!

What do you use as an input fields? I want to send Additional comments, Jira Project, Description, State.

Have you got any other good resources for Jira Hub integration? My client wants me to use the Hub because it is not involve scripting, and so -- easier than the classic way. So I decided to be sporty and took the challenge. Now I am extremely annoyed by the lack of documentation. "Atlassian Jira Integration Common", for example, has extremely interesting looking actions, but they don't even have a description! 😕

ServiceNow Tec2 · ‎08-17-2020

This has been resolved by ServiceNow Technical Support. Please refer to KB0818292 for more information.

Vladimir6 · ‎09-02-2020

"To overcome this, you would need to populate the Issue ID with a valid record."

No guys, to define a single Issue ID is not a resolution. What if I need to find the Issue first, or I need to loop through the list of Issues?

KB0818189 is the resolution, or IMHO a workaround.