OVERALL RATINGS
INSTALLS
1
SUPPORT
- Partner Supported
TRUST SIGNALS
Key highlights of the appCustomer portal attachments an agent or the Jira create screen added stay invisible — this panel lists and downloads them
Files the portal never shows the customer
A file attached on the Jira create screen, or by an agent, is carried by no comment, so the portal does not list it. This panel does, with filename, size, type, who added it and when — and it downloads.
A file on an internal comment is never listed
An attachment carried by an internal comment is never listed and never downloadable. That is not a setting, has no switch, and is re-decided on the download route before a single byte is fetched.
One policy, site-wide or per project
Reporter uploads are shown by default, so a fresh install lists files before anyone opens a settings page. Turn agent uploads on site-wide, or override the policy per project, and read a live count of what is exposed.
More details
Jira Service Management’s customer portal lists a file only when a public comment carried it. A file attached on the Jira create screen, or by an agent working the request, is carried by no comment at all — so the customer looking at their own request cannot see it or download it. JSDCLOUD-4646 asks Atlassian for exactly this and carries 131 paid support references.
This app renders a side panel on the portal request listing those files: filename, size, type, who added it and when. Each downloads through the app, because no Jira route hands an attachment to a portal customer directly.
What is listed is decided on every read from Jira’s own facts — who attached the file, who reports the request, who participates, and whether a public or an internal comment carried it. The app stores a policy, never a decision: nothing it persists names an attachment, so uninstalling changes no Jira data. A file an internal comment carries is never listed and never downloadable.
Resources
App documentation
Comprehensive set of documentation from the partner on how this app works
Privacy and Security
Privacy policy
Atlassian's privacy policy is not applicable to the use of this app. Please refer to the privacy policy provided by this app's partner.
Partner privacy policySecurity program
This app is not part of the Marketplace Bug Bounty program.
Integration permissions
Portal Attachments for Jira Service Management integrates with your Atlassian app
Version information
Version 2.0.0•for Jira Cloud
- Release date
- Sep 18th 2026
- Summary
- First release: the portal panel that lists the files JSM itself does not show
- Details
First release.
- A side panel on the Jira Service Management customer portal request, listing the attachments the policy admits: filename, size, MIME type, who added it and when.
- - Download of a listed file, with the bytes proxied through the app’s own resolver.
- - A visibility policy computed on every read from native Jira facts — attachment author, request reporter, request participants, and whether a public or an internal comment carried the file. Nothing per-attachment is stored.
- - A hard rule with no setting: a file carried by an internal comment is never listed and never downloadable, and the download route re-decides before it fetches anything.
- - An admin page holding the site-wide policy, a per-project override table, and a live count of what the panel is currently exposing.
- - Reporter uploads are shown by default, so a fresh install lists files with no configuration step.
- - Runs entirely on Atlassian: Forge modules only, Forge storage only, and no egress.
- Payment model
- Paid via Atlassian
- License type
- Commercial