Jira Spoke - Integration Hub - bi-directional (Rome Version) 2022

Jira Spoke - Integration Hub - bi-directional (Rome Version) 2022
1. Outbound Integration
Using "Create Issue" Action
2. Inbound Integration
Using "Process Webhook" Subflow
3. Troubleshooting
Using "Operational Execution"
Next video coming up by using "Update Issue" and generate additionalfields (Stay Tunned!!)
Jira Spoke integration from docs:
docs.serviceno...

[@DrxThmSklnst]

Hi Satz. how did you do in Jira where the reporter is the caller in servicenow, right now in our instance it just shows Reporter: "ServiceNow". Thank you!

[@techoclock8367]

For some reason, the subflow is not trigerring. And I followed you every step of the way.

[@sudhangshudas3099]

Thanks for this!! Worked like it should. Great going.👍

[@aishwaryapandit6431]

I am facing the issue in integrating bi- directionally in utah release i.e. from jira to servicenow as I have created webhook and configured flow and update the short description in jira so that it can be changed in servicenow instance record as well but there is no update in servicenow from jira.

[@darkomarkovski7902]

i dont have connection alias filed in the flow and i cannot call the jira help

[@sureshkumar-zp6hf]

hey , i configured as it is but i am unable to see connections alias field in flow desginer create issue section.please help

[@surajnikam9894]

Thanks for the video. I am facing issue in generated API token and unable to create credentials stating "Password value is too long"

[@charanreddy...............6526]

Change the Password field max length to 1000 then it's works fine.

[@manoramu8654]

im not able to see connection alias in the flow

[@bekkafroehlich5757]

The connection alias will not show after San Diego. Once you get the populated fields from Jira you know you have a connection.

[@fazzukhan2459]

bro km se sahi se to explain krde yrr