Sync Comments Between ServiceDesk Plus and Jira Without Leaking Internal Notes
The day comment sync goes live, somebody will write an honest internal note — and it will appear in the other system, in front of a wider audience than intended. It happens to almost every team once. This page exists so it happens to you zero times.
✍️ Technical Anshu🎫 ServiceDesk Plus + Jira⏱️ 6 minute read
🎥 Watch the full setup in the video — every click, step by step
ManageEngine's Jira app for ServiceDesk Plus can sync notes and comments between the two platforms — genuinely useful, because questions stop dying in whichever system the other team never opens. But the two products divide comments differently: ServiceDesk Plus separates requester-visible replies from technician notes, and Jira (especially Jira Service Management) separates public comments from internal comments. Sync is safe only when those two dividing lines are respected.
Comment types — what crosses, what stays home
SDP requester reply — "Try the new build"SYNCS
Jira public comment — "Fix is in testing"SYNCS
SDP internal note — "Vendor bug, again"STAYS HOME
Jira internal comment — candid triage talkSTAYS HOME
SDP note — "User shared password in ticket"STAYS + ACT
The dividing line is audience, not convenience. If the requester should not read it, it does not travel. Example entries, shown as an illustration.
1
Know the Two Dividing Lines Before You Enable Anything
ServiceDesk Plus: replies and conversations are what the requester sees; notes are the technicians' private scratchpad on the ticket.
Jira: comments on a plain Jira Software issue are visible to everyone with project access — a wider audience than most people assume. Jira Service Management adds explicitly internal comments.
The safe rule writes itself: sync the public layer both ways; keep the private layers home.
If your setup offers a choice of what to sync, choose the public layer only, even if syncing everything looks more "complete" in a demo.
2
Set the Sync Rule, Then Test It with a Trap
Configuration is five minutes. Verification is where you earn it:
On one linked pair, add a public reply in ServiceDesk Plus — confirm it appears in Jira.
Add a public comment in Jira — confirm it appears in the request.
Now the trap: add an internal note in ServiceDesk Plus with harmless test text — confirm it does not appear in Jira.
Repeat from the Jira side with an internal comment if your Jira setup has them.
Only after the trap test passes both ways do you tell the teams sync is live.
3
Teach the One Sentence That Prevents 90 Percent of Leaks
Technology handles the configured line; humans handle everything else. Give both teams one rule, in writing, in the announcement itself:
"If it syncs, write it like the user is reading." Because with linked tickets, they effectively are — or soon will be.
Candid diagnosis, vendor frustration, and "the user probably caused this" belong in the internal note, always, even when you are in a hurry.
Credentials and personal data never belong in comments at all — synced or not. If a user pastes a password into a ticket, remove it and tell them to change it.
4
Handle the Day It Goes Wrong Anyway
Plan for the leak so the response is calm, not improvised:
Delete or edit the comment in both systems — removing it on one side may not remove the synced copy.
Check whether the requester actually saw it (portal notifications and email copies go out fast).
If it contained anything sensitive — credentials, personal data — treat it as a small security incident, not an embarrassment: rotate what was exposed.
Re-check the sync settings afterwards; most leaks are a configuration that silently included notes, not a careless person.
🔴 The trap test is not optional. Sync one internal note on purpose, in a test ticket, before go-live. The five minutes it takes is the cheapest insurance in this entire integration.
🎥 Watch the Complete Video
The full Jira and ManageEngine sync setup — live demo, step by step, in the video.
Does the ManageEngine Jira app sync comments and notes
Yes — ManageEngine documents that notes and comments can be synced between ServiceDesk Plus modules and Jira issues. Which comment types you include is a configuration choice, and the safe default is requester-visible conversation only, keeping internal technician notes at home.
A synced comment was edited later — does the edit sync too
Treat synced comments as published. Edits and deletions do not reliably chase copies across systems in every tool, so write synced comments carefully the first time, and if something must be corrected, check both systems by hand.
Should developer comments go straight to the requester
Only the public layer should. A developer writing "fixed the null check, deploying Thursday" is perfect for the requester. A developer writing a candid triage debate is not. The public/internal split exists precisely so both kinds of writing have a safe home.
This guide is based on the Technical Anshu video on syncing Jira with ManageEngine • Stuck on a step? Ask in the video comments — answers happen there 🙏