Community resources
Community resources
Community resources
The Change Was Approved in ServiceNow. Nobody in Jira Knew It Started
I work in support and services at Exalate, and I recorded a live demo of the workflow in this post, so consider that my disclosure up front.
Here's the setup I keep running into with customers who run ServiceNow and Jira side by side. The CAB sits in ServiceNow and does its job there. The people who actually implement the change, the engineers, live in Jira or Jira Service Management. Somewhere between "approved" and "done," that handoff usually turns into someone copying a ticket number into a comment and hoping the other team notices.
Where Does the Handoff Actually Break?
Not at approval. CAB review, risk assessment, sign-off, all of that works fine inside ServiceNow on its own.
It breaks the moment the change needs to leave ServiceNow and become work for a Jira engineer. Someone has to notice the change is ready, open Jira, create a ticket, paste in the implementation plan, and then go back and forth checking status. For a single change, that's tolerable. Across a busy CAB queue, it's a full-time job nobody signed up for.
What Should Happen the Moment a Change Is Authorized?
Here's what I set up and walked through in the demo:
A change request stays in ServiceNow through assessment and CAB authorization. Jira doesn't see it yet, and the engineer isn't pulled in before there's anything real for them to do.
Once the CAB approves it and the change moves to "Scheduled," Exalate creates the Jira issue automatically on the right board. The description, the justification, and the full implementation plan come across with it. The ticket number flows straight back into the ServiceNow record, so the CAB can see the Jira issue exists without asking anyone.
The engineer opens a ticket that already has everything they need. No emailing the change owner to ask what the plan was.
Does the Sync Stay Current Once Work Starts?
Yes, and in both directions. When the engineer adds a comment and moves the Jira ticket to "In Progress," ServiceNow automatically advances the change to "Implement." Nobody has to update ServiceNow by hand for the CAB to know work has started.
Comments sync too, but not all of them. In the demo, I added an internal work note on the ServiceNow side ("hope these guys do it quickly") and a public comment ("thanks"). Only the public comment showed up in Jira. The internal note stayed internal, which matters if your CAB writes anything they wouldn't want a vendor or a customer-facing engineer to read.
I also edited the implementation plan after the ticket was already created, just to see what happened. The change synced through to Jira within a refresh. More importantly, the Jira history logged that Exalate made the edit and when. That's the part that matters when someone reviews the ticket later and needs to know whether a human or the integration changed the field.
What Happens When the Work Is Done?
Closing follows the same pattern. Mark the Jira ticket done, and the status flows back to ServiceNow: implement, then review, then closed. Every transition writes to the audit trail on both systems, not just one.
That last point is the one people underestimate. When an incident review asks "did this go through change management, and who did what when," you want a complete answer on both systems. Not a Jira history that stops mid-story because the rest of the update happened over email or Slack.
The Config Behind It
None of this needs a custom integration built from scratch. It runs on a sync engine with scripts controlling the logic in both directions, ServiceNow to Jira and Jira to ServiceNow. You decide what data crosses over, which fields map to which status, and which comments stay private. If your CAB workflow looks different from a textbook ITIL flow, that's fine. The mapping is configurable, not fixed.
If you want to read Atlassian's own breakdown of the change management workflow and CAB approval steps in Jira Service Management, it's worth a look: Best practices for change management.
For anyone who wants to see the tool itself, here's the Exalate listing on the Atlassian Marketplace.
Key Takeaways for Atlassian Teams
- Keep the change in ServiceNow until it's actually authorized. Don't pull Jira in early.
- Auto-create the Jira issue on "Scheduled," with the full implementation plan attached, not just a summary line.
- Map status changes both ways so the CAB sees progress without asking for it.
- Filter internal notes out of the sync. Public comments cross over, internal ones don't.
- Keep both systems' audit trails complete. Half a history is worse than none when someone needs to reconstruct what happened.
How does your team handle the CAB-to-engineering handoff today? Curious if you're doing this manually, or if you've automated pieces of it already.