I was at Team '26 in Anaheim last week. The keynotes were good. The AI announcements were expected.
What caught me off guard was how many enterprise teams are still wrestling with the same fundamental problem: getting ServiceNow and Jira to actually work together.
The use cases weren't identical. There were really 4 patterns that kept coming up.
ITSM to dev handoffs
IT Ops lives in ServiceNow. Engineers live in Jira. When a P1 lands, someone manually copies it across, chases updates in Slack, and tries to reconcile 2 tickets that were never truly in sync. Teams weren't looking for a new tool. They wanted the 2 tools they already use to stop fighting each other.
Change management
ServiceNow owns the CAB process. Jira owns the actual development work. Without a sync, you get CAB approvals on one side and dev tasks on the other, disconnected, with no audit trail to show they ever spoke. Compliance teams aren't fans of that.
JSM as the service desk, ServiceNow as the ITSM platform
This one comes up a lot with larger enterprises. The internal IT team runs Jira Service Management for first-line support. Their shared services or outsourced provider runs ServiceNow. When a ticket needs to escalate or gets handed off between teams, someone ends up copying fields manually, or worse, maintaining 2 separate ticket threads on each side with no real sync between them. SLA accountability breaks down fast in this setup.
Cross-company collaboration
This one surprised me the most.
A company in ServiceNow needs to work with a client or vendor in Jira. Neither side wants to change their tooling. A contractor managing work in Jira needs to report progress to a client whose ITSM platform is ServiceNow. The integration is the only realistic path, and it has to handle field mapping, comment sync, and status updates in both directions without either team needing access to the other's system.
But what really stayed with me were two conversations.
A team from Detroit had built their own integration between ServiceNow and Jira. Sounded like a win to me. But then they were a little more honest about it. Every API change, every system update, every new workflow someone added meant going back in and fixing it.
The maintenance cost had grown to the point where it was consuming more than the value it was delivering. Engineering time that should've gone to product work was absorbed by keeping the connection alive.
Then a very large enterprise told me they'd skipped all of that. They were still handling ServiceNow to Jira handoffs manually. Emails. Copy-paste. A person on each side acting as the human middleware. In 2026, really?
I see two different failure modes here, but the same root problem.
None of this is a niche edge case. It's structural, built right into how large organizations adopt tools by department, by mandate, by legacy decision.
ServiceNow isn't going anywhere. Jira isn't going anywhere. And JSM teams don't want to lose control of their support workflows just because the ITSM platform on the other side is different.
If any of these patterns sound familiar, happy to share what we've seen work. Drop a comment or reach out directly.
