Sync Jira with ManageEngine ServiceDesk Plus Complete Setup Guide

Most failed integrations fail here, before any setting is touched. Write down three answers first:

1. Which side creates work? Usually: support raises requests in ServiceDesk Plus; when a request needs development, a Jira issue is created and linked.
2. What must the other side see? Status and priority for the help desk; the problem description and user impact for the developers.
3. What must never cross over? Internal technician notes, salary/HR tickets, and anything marked private. Decide this now, not after an embarrassing sync.

The video walks through the connection screens click by click; this page gives you the decisions those screens are asking you to make.

Use ManageEngine's own Jira app rather than a random connector — it is built and supported by ManageEngine for ServiceDesk Plus.

1. In ServiceDesk Plus, open the admin / apps area and install the Jira app from the ManageEngine Marketplace.
2. Enter your Jira site address, for example https://yourcompany.atlassian.net for Jira Cloud, or your Jira Server / Data Center URL.
3. Authenticate with a dedicated sync account (never your personal admin login — see the security card below). For Jira Cloud this normally means the account's email plus an API token created in that Atlassian account.
4. Pick which Jira projects technicians may create and link issues in. Start with one pilot project.
5. Save, then run the connection test the app offers. Do not skip the test — a green test here saves an hour of guessing later.

With the connection live, the everyday flow is deliberately boring — that is the point.

1. Open a request in ServiceDesk Plus that needs development work.
2. Use the Jira option on the request to create a new Jira issue (subject and description carry over) or link an existing issue by its key, like NET-231.
3. The same linking works from the Problems, Changes, Assets and Releases modules, not just requests.
4. Open the request again: the Jira issue's subject, priority, status and assignee now display inside ServiceDesk Plus and stay updated.

One honest note: linking is the foundation. A ticket nobody linked will not sync, no matter how good the app is — make "link it when it goes to dev" a team habit.

The official app can sync notes and comments between ServiceDesk Plus modules and Jira issues. This is the feature users feel most — and the one that can hurt you if you switch it on blindly.

1. Sync only public / requester-visible conversation by default.
2. Keep internal technician notes on the ServiceDesk Plus side only. A note that says "user keeps breaking this" should never appear in Jira where a wider audience reads it.
3. Test with one linked pair: comment on the Jira issue, confirm it lands in the request; reply in the request, confirm it lands in Jira.
4. Tell both teams the rule in one line: write every synced comment as if the other team — and the user — will read it. Because they will.

ServiceDesk Plus and Jira workflows do not line up one-to-one, and pretending they do is the top cause of "the sync is lying" complaints. ServiceDesk Plus typically runs Open, In Progress, On Hold, Resolved, Closed. A dev team's Jira workflow might run To Do, In Progress, Code Review, Testing, Done.

1. Draw both status lists side by side and decide what each Jira status should show as on the support side (Code Review and Testing usually both read as In Progress for the requester).
2. Agree the two statuses users actually care about: work has started and work is finished. Everything between is detail.
3. Decide whether a Jira Done may close the ServiceDesk Plus request automatically, or only mark it Resolved so a technician can verify with the user first. For user-facing tickets, verification-first is usually the honest choice.

So nobody oversells this in a meeting:

1. The official app is a link-and-visibility integration: create and link issues, track their key fields inside ServiceDesk Plus, and sync notes and comments. It is not a full mirror of every custom field on both sides.
2. If you need deep two-way field sync — every custom field, workflow transition and attachment mirrored both ways — that is a job for a dedicated sync platform (tools such as Exalate or ZigiOps exist for exactly this), with its own licence cost.
3. "Instant" means seconds-to-minutes on a healthy connection, not zero. If a status looks stale, wait a moment and refresh before declaring the sync broken.
4. Old, already-closed tickets do not backfill themselves. The sync works from the moment things are linked.