- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-22-2020 11:38 AM
Flow Designer > Jira Spoke 2.6.5 > Update Issue > Additional Fields "Add Field Value" is grey out?
Is this expected? Or should I be able to add field values to other Jira Issue fields?
Any info is appreciated... Thanks!!
Solved! Go to Solution.
- Labels:
-
Integrations
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-22-2020 05:02 PM
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!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-22-2020 05:02 PM
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!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-23-2020 05:43 AM
Those are the steps we followed and worked for us. It's unfortunate that it's necessary to do so ServiceNow.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-25-2022 05:43 AM
We use this method but when moving Flows from environment to environment, if the issue ID you are using does not exist in the target Jira instance it breaks down
So do not edit Flows in Target environments and your configuration should remain.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-21-2022 07:01 AM
That's good solution provided by Michael however there few bugs to find out unless you know how to enable property for parse the JSON in custom action.
Here is the video you can find it and it's description have the links to KBs
https://www.youtube.com/watch?v=Vqthvk2nIEA