Can't connect to Jira from ServiceNow instance
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-07-2025 11:40 AM
I am trying to establish a connection from our ServiceNow instance and Jira, and cannot, for the life of me, get it to work. I've followed all the steps in the guided setup, and am seeing this when I click connect from my Jira instance with in SeriveNow: "A connection cannot be established. Please check the system logs for details." In the error logs I see:
"Cannot establish connection to Jira, StatusCode:"
"Error on Register Webhook to Jira Action: org.mozilla.javascript.NativeJavaObject@cab012bd"
We've registered the webhook in the Jira Instance and have valid credentials.
All relative applications are up to date too. What am I missing here?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-07-2025 03:43 PM
Hello @mpsteve137
Please check the system logs for the exact error trace.
Full error stack trace related to Jira.
Any 401 Unauthorized, 403 Forbidden, or 500 Internal Server Error messages.
If you see 401 Unauthorized, reconfirm credentials.
If 403, ensure the Jira integration user has permissions to register webhooks.
If 500, Jira’s API may be rejecting the request due to malformed payloads
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-07-2025 07:09 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-07-2025 08:19 PM
Hi @mpsteve137
I hope you are reffering this document.
https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0792632
Mark it helpful and accept solution!!! if this helps you to understand.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-18-2025 04:46 AM
Dear @mpsteve137
You might want to give Exalate a try—it handles Jira-ServiceNow connections with fewer setup headaches and more flexibility. Could help bypass issues like the one you’re hitting with the webhook.