Sync Attachments Between ServiceDesk Plus and Jira and Their Real Limits
A ticket without its screenshot is a riddle. A Jira issue without the log file is a guessing game. Attachments feel like they should just sync — and mostly they do, right up until a 40 MB log bundle meets a limit nobody knew existed.
✍️ Technical Anshu🎫 ServiceDesk Plus + Jira⏱️ 6 minute read
🎥 Watch the full setup in the video — every click, step by step
Attachments are where the two systems' different personalities collide. ServiceDesk Plus receives whatever a user emails in. Jira has its own attachment size settings. Any sync between them inherits both sets of limits, plus a few behaviours — copies versus links, blocked file types, duplicate-on-resync — that are invisible until they bite. Here is what to expect and how to find your real numbers before your users do.
Attachment sync — one file's journey
screenshot.png 1.8 MBSYNCED
error-log.txt 6 MBSYNCED
full-logs.zip 48 MBTOO LARGE
installer.exe blocked typeREFUSED
screen-recording.mp4 210 MBLINK INSTEAD
Small evidence files fly across; bulk and executables do not. Your exact limits depend on both products' settings. Example entries, shown as an illustration.
1
Copies, Not Windows — Know What Your Sync Actually Moves
Two designs exist, and they age very differently:
Copy sync — the file itself is duplicated into the other system. Robust (the file survives even if the original ticket is deleted) but storage doubles, and editing one copy never updates the other.
Link sync — the other side gets a reference back to the original file. Light and always current, but it breaks for anyone who lacks permission on the source system — which is often the whole reason the file was being shared.
Check which design your setup uses before promising behaviour to either team, and remember: ManageEngine's built-in app focuses on linking issues and syncing conversation — heavy attachment mirroring is typically a third-party sync tool feature. Set expectations accordingly.
2
Size Limits — the Smaller Ceiling Wins
Both products let administrators cap attachment size, and the sync can only move what both sides accept.
The realistic clash: users email log bundles and screen recordings that sail into ServiceDesk Plus and then hit Jira's ceiling on the way across.
Decide a house rule for big evidence: small files sync; big files live in one agreed place (a file share or cloud folder) with a link pasted into both the request and the issue.
Write the limit down where users can see it, so "the sync ate my file" stops being a support ticket of its own.
3
Blocked Types Are a Security Feature, Not a Bug
Executable attachments — .exe, scripts, installers — are refused by many setups on one or both sides, and that refusal is correct. A sync that happily ferried executables between systems would be a malware distribution feature with extra steps. Teach the workaround instead: screenshots of the error, exported logs as text or zip, and links to installers on your official software share — never the installer itself riding through a ticket.
4
Duplicates and Edits — the Quiet Mess
If sync re-runs (after a settings change or a reconnect), some tools cheerfully upload the same file again. Check one linked pair after any reconfiguration.
A file replaced on one side is usually a brand-new attachment to the sync, not an update — the other side keeps the old version too. Version discipline ("logs-v2.txt") beats silent replacement.
Deleting an attachment on one side rarely deletes the copy on the other. If a file contained something sensitive, delete it in both places and say so in the ticket.
5
The Five-Minute Attachment Test
Before go-live, run one linked pair through: a screenshot, a medium text log, a zip near your expected limit, and one deliberately oversized file. Watch what arrives, what is refused, and what the failure looks like from the user's side. Whatever surprises you in the test would have surprised a user in production — tests are where surprises belong.
🔴 House rule worth stealing: evidence under the limit syncs automatically; anything bigger lives in one agreed folder, linked from both systems. It ends the size-limit argument permanently.
🎥 Watch the Complete Video
The full Jira and ManageEngine sync setup — live demo, step by step, in the video.
Do attachments sync with the built in ManageEngine Jira app
The built-in app centres on creating and linking Jira issues, tracking their status, priority and assignee, and syncing notes and comments. Full attachment mirroring is generally a feature of dedicated third-party sync platforms. Confirm the current app listing for your edition before planning around it.
What happens to a file that is too large to sync
Typically it stays in the system where it was uploaded and simply does not appear on the other side — sometimes silently. That silence is why the house rule matters: agree a shared location for big evidence and paste the link into both the request and the issue.
A user attached the same screenshot five times — will the sync clean it up
No. Sync tools move what exists; they do not judge it. Duplicates on the source become duplicates (or repeated copies) on the other side. Clean the source ticket if the clutter matters, and coach the user rather than fighting the tool.
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 🙏