Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

The 4 Integration Gaps I Kept Hearing About at Atlassian Team '26

I spent 3 days at Atlassian Team '26 talking to Jira and JSM teams about their integration setups. Four problems came up in almost every conversation.

Not edge cases. The same four gaps, over and over.

Gap 1: Change Management, the CAB approval black hole

ServiceNow owns the CAB process. Jira owns the dev work. Between them, there's usually nothing. Approvals sit in ServiceNow, tasks sit in Jira, and someone copies data between them by hand.

The teams that tried to automate it built in-house APIs that kept breaking. That maintenance cost doesn't show up on any dashboard, but it's real.

Here's what actually works: a CAB approval in ServiceNow creates a linked Jira issue automatically. Statuses and public comments move both ways. Internal notes stay private. When Jira hits "Done," ServiceNow resolves on its own.

Gap 2: ITSM-to-Dev handoffs for P1s

IT gets the incident. Engineering needs to fix it. The handoff between ServiceNow or JSM and Jira Software is where time gets lost.

I've seen support engineers log into Jira, create a ticket manually, then go back to ServiceNow to update the customer every hour for every P1. Automated escalation based on priority and category fields cuts that to zero manual steps. The dev team gets full context. The support team gets status updates without touching Jira.

Gap 3: JSM vs. ServiceNow escalation tiers

A lot of organizations run both. JSM for internal IT, ServiceNow for enterprise ITSM, or vice versa. When a ticket crosses systems, the originating team goes blind. They're emailing for updates instead of seeing them in their own tool.

Bidirectional sync between JSM and ServiceNow keeps both teams in their native tools, with real-time visibility on both sides.

Gap 4: Cross-company collaboration

You're syncing with a vendor, a client, or an external partner and you can't give them access to your Jira instance. Security won't allow it, and you shouldn't want it either.

The answer is controlled sync. Each side sees exactly what you decide to share. Field-level control, comment-level control, and a full audit trail. 

Come see all 4 with a live demo

On June 24, I'm co-hosting Sync Room, a live session covering all 4 patterns with demos and time for your specific questions.

SRW-E05-image-04.png

 

🗓️ June 24, 2026 | 4:00 PM Brussels / 10:00 AM ET
Register here

I work at Exalate, and we built the connector that handles these patterns. You can find it on the Atlassian Marketplace. The session itself is practical. Bring your use case, and we'll dig into it.

0 comments

Comment

Log in or Sign up to comment
TAGS
AUG Leaders

Atlassian Community Events