Bi-directional Integration with Jira with IntegrationHub and Flow Designer

Community Alums · ‎08-02-2023

Hello,

I configured bi-directional Integration with Jira with IntegrationHub and Flow Designer. For inbound (from Jira to ServiceNow), it is showing "No decisions matched" in logs in ServiceNow. To create Jira WebHook Routing Policies, I took the reference from the OOTB record. And in Jira, I register a WebHook.

For outbound (from ServiceNow to Jira), it is working fine.

SS:

How do I resolve this?

Thank you!

Community Alums · ‎08-04-2023

Hello @Kiran Raddy ,

I tried multiple things, but anything did not work for me. Finally, I took these steps, and they worked for me:

1. I uninstall "Jira Spoke" and reinstall it again, referring to this video (and performed the entire steps the same): https://youtu.be/lqnOurQlM_U

2. As I am testing this integration, my Jira instance is a demo instance, not a client environment, so I create a new Jira instance, not using the earlier one.

3. And my ServiceNow instance is domain-separated, so I configured everything on the global domain this time and gave the correct conditions in flow so that it runs on the required domain.

@Kiran Raddy , I'm hoping it will work for you too.

Thank you!

View solution in original post

Kiran Raddy · ‎08-04-2023

@Community Alums

OOTB JIRA decision is active false. Navigate to list layout or add the field to the form layout, update it to Active "true" to make this work as expected. Below is the attached image.

hope this helps !

Please mark my answer as correct/helpful based on its impact to help other users.

Community Alums · ‎08-04-2023

@Kiran Raddy , In my case, that was active.

Kiran Raddy · ‎08-04-2023

@Community Alums , Okay. In that scenario, the above post might help other users.

As I checked, in list layout, was active false. Because as I search and click "Jira WebHook Routing Policies" opens a record and the view is "Jira Webhooks" and it doesn't display active field. If we change it to default, then it will.

Megalithe · ‎04-18-2024

Incase anyone encounters this issue in the future I found the solution for my occurrence.
Post upgrading our Servicenow Platform Version, it appears the Decision table added a second entry that overwrote the priority of my decision custom table.

The decision table that it was using was just a blank table, hence the error message in the system log.

I considered resetting the priority but this lead to unintended results so I deleted the duplicate and this resolved the issue.