Documentation
Jira Service Management's customer portal shows a customer only the files a public comment carried. 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.
Portal Attachments adds a Files panel to the portal request that lists those files — filename, size, type, who added it and when — and lets the customer download them. A file carried by an internal comment is never listed and never downloadable.
Email support@maxpetrov.pp.ua. There is one address and it is read by the person who wrote the app.
Say which request you were looking at, what you expected to see in the Files panel, and what the admin page under Apps shows for the site policy and for that request's project. If a file you expect is missing, two things decide it: whether an internal comment carries that file, which is never listed by design, and whether agent uploads are turned on for that project. Both are readable on the admin page.
There are exactly two places this app appears, and nothing else in Jira changes.
The customer portal request. Open any request in your service desk portal — the URL looks like /servicedesk/customer/portal/1/HSM-1 — and look down the right-hand column, under Apps. The panel is titled Files. If every file on the request is already shown by a public comment, the panel says so rather than showing nothing.
The admin page. Jira administration, then Apps in the left-hand nav, then Portal Attachments. This is where the site policy, the per-project overrides and the live exposure count live. You need Jira administrator rights to open it.
The decision is recomputed on every read from Jira's own facts — who attached the file, who reports the request, who participates in it, and whether a public or an internal comment carried it. Nothing per-attachment is stored, so uninstalling the app changes no Jira data.
Always listed: a file on a public comment, exactly as the portal already shows it.
Listed by default: a file the reporter or a request participant added, including one added on the Jira create screen, which no comment carries.
Listed when an administrator turns it on: a file an agent or any other Jira user added.
Never listed, with no setting and no switch: a file carried by an internal comment. The download route re-decides before it fetches a single byte, so asking for such a file directly is refused as well.
Open Apps, then Portal Attachments, in Jira administration. Two switches decide what the panel adds beyond what the portal already shows: show files the reporter or a request participant added, and show files an agent or any other Jira user added.
Reporter uploads are on when the app is installed, so a fresh install lists files before anyone opens this page. Agent uploads are off.
Below the site policy is a table of every service desk project on the site. Saving an override there makes that project ignore the site policy. Clearing it puts the project back on the site policy. Up to 200 projects can carry an override.
At the top of the page is a live count — how many files on the most recently updated requests are visible in the portal right now, and how many of those would not be visible without this app. It is produced by the same decision the panel runs, so it moves when you change a switch.
These are limits of the app as shipped, not faults. They are the same list the Marketplace listing carries.
Anonymous portals are not supported. The Forge module this app renders in works for customer and unlicensed accounts and states that it does not support anonymous access, so a portal that allows unauthenticated customers will not show the panel to them.
The panel does not upload. Jira Service Management's own comment box owns upload on the portal and this app adds no second one.
The app never deletes, renames or re-orders an attachment. It declares no write scope of any kind.
Configuration is site-wide with a per-project override. There is no per-request-type and no per-attachment setting.
No thumbnails, no inline previews and no bulk or zip download.
A file larger than 3 MiB is listed with its size and a message, and is not downloadable in the panel; the ceiling is the Forge front-end response payload limit, which a base64 body of a larger file would exceed.
Above 150 attachments on one request the panel lists the newest 150 and states how many are not listed.
Nobody is notified when a file becomes visible. Turning a policy switch on does not email a customer, and the panel sends no notification of any kind.
Cloud only. There is no Data Center or Server version, and the app does not work in Confluence or in non-JSM Jira projects.
The app runs entirely on Atlassian infrastructure. It declares no remote hostname and calls no external service; nothing it reads leaves Atlassian. It stores a policy — two switches for the site and two per project with an override — and nothing else. Nothing it stores names an attachment, a request or a person.
The full privacy policy is published separately and is linked from the Marketplace listing.