DOCUMENTATION
.png)
Specs & security
What Bulk Comments for Jira requires, what it can reach, and where your data goes.
v4.8.0 — Latest
Runs on Atlassian
Atlassian Forge
Jira Cloud
Technical specifications
| Detail | Value |
|---|---|
| Platform | Atlassian Forge (Cloud only) |
| Product | Jira Cloud — Jira, Jira Service Management, Customer Service Management and Jira Product Discovery |
| Installation | Atlassian Marketplace |
| Licensing | Free for teams up to 10 users; paid tiers above, billed through the Atlassian Marketplace. See the pricing calculator for current rates. |
| Issue Limit | Up to 25 issues per send. On a service project a request can carry two comments, so a full batch is up to 50 comments across 25 requests. |
| Per-issue comments | Every issue gets its own independent comment, written and attached on its own composer |
| Comment visibility | Service projects only. Every comment on a Jira Service Management or Customer Service Management request is explicitly an internal note, seen by agents alone, or a reply to the customer, which reaches them on the portal and emails them. The choice is made per request. |
| Two comments per request | Service projects only. A request can carry both at once — the customer reply and the internal note that accompanies it. They are written separately and posted together in one request’s work, internal first, so they cannot land out of order — which is why the composer shows the reply on top and the internal note beneath it, the way Jira will display them. |
| How visibility is set | Through the sd.public.comment property on Jira’s own comment API. It is always written explicitly: measured on Cloud, omitting it posts the comment publicly, so the app never leaves it to a default. Whether an issue is a service request is resolved from Jira at send time, not from the browser, and an unresolvable issue is treated as a service project so the comment lands internal. |
| Product vocabulary | The app calls them ideas in Product Discovery, requests on a service project, and issues everywhere else, following the issues you selected. |
| Per-issue status changes | Move each issue as you comment on it, chosen from that issue’s own workflow as it stood when the step opened, so only transitions Jira would accept are offered. If somebody moves the issue before you send, the app says so and asks you to reload and pick again. A status change counts on its own — an issue needs no comment to be included. A status change cannot be reversed from the app; move it back in Jira. |
| Delivery | Comments posted per issue with live sending / delivered / failed / not-sent status. Retry re-runs failures and issues the send never reached; a status change Jira refused is counted separately and skipped by retry, because that issue’s comment is already in Jira. |
| Send time budget | A Forge resolver gets 25 seconds. The app stops starting new issues with time to spare and answers normally, reporting the remainder as not sent — a known partial result that is safe to retry, rather than an invocation killed with no result at all. |
| Large-batch Confirmation | The send guard: a confirmation before posting to 10+ issues, sending a comment that @mentions someone, or attaching 50 MB or more — which names the storage the send will add so you can confirm you have room. Separately, if a send is interrupted and returns no result, Send is held until you confirm you have checked Jira. |
| Media Support | Images, videos and file attachments up to 150 MB each. Images and video play or preview inline in the app; other files open in Jira. |
| Per-file Limit | 150 MB per file — the ceiling is per file, not per comment, and one comment can carry as many files as you need. Checked the moment you attach, not at send. If your Jira site sets a lower attachment limit, that one wins. |
| Per-send Limit | 2 GB written into Jira per send. A file is written once for every issue it lands on, so the figure is file size × issue count — see Limits. A larger send is refused before it starts, so nothing is posted; split it into smaller batches and the total resets per send. |
| Storage Estimate | Named in the confirmation once a send moves 50 MB out of the browser or writes 250 MB into Jira — either alone is enough. A shared file is uploaded once and fanned out by the backend, so upload size does not multiply by issue count but storage does: 150 MB across 9 issues is 150 MB uploaded and 1350 MB written. Nothing is posted if a send would breach the 2 GB ceiling. |
| Large Media Handling | Uploaded through an async queue for large files, so a big video does not block the send while it uploads. Very large files across many issues can still exceed the platform’s upload window, in which case nothing is posted. |
| Comment History | An issue’s panel shows its 25 most recent comments, in full — with images, video and files — not just a preview. The panel follows whichever composer you are writing in, and a list down the left jumps between the issues in the batch; both keep their width between sessions. |
| Runs on Atlassian | Yes — verified by Atlassian. The app runs entirely on Atlassian infrastructure with no external data egress. |
| Data Storage | Atlassian Forge Storage — no external servers, data stays in Atlassian cloud |
| Personal data | The app keeps no user records. Forge storage holds only per-send job status — state and timestamp — while a send is running; comments pass straight through to Jira, and attachments are staged only in transit and discarded once Jira has them. No external egress is declared, so nothing reaches a DataPingo server, and uninstalling removes everything the app stored. |
| Permissions | Read & write Jira work items (writes use impersonation, so you are the author); read Jira user profiles; app storage |
| Themes | Light & dark, following the colour scheme Jira renders the app in |
| Access Points | Apps in the left sidebar, or an issue’s ••• actions menu |
| Status | Published — live on the Atlassian Marketplace |
System requirements
- Active Jira Cloud instance — any Jira product, including Service Management and Customer Service Management
- Modern web browser (Chrome, Firefox, Safari, Edge)
- Active internet connection
- Appropriate Atlassian Marketplace license
Permissions required
Four scopes, and no others:
read:jira-work— read the issues and comments you select, so they can be listed, searched and previewed with their full history and media. These reads happen inside your own session, as you.write:jira-workallowImpersonation — post the comments and upload their attachments.read:jira-user— resolve names for @mentions and show who authored a comment.storage:app— the app's own storage on Atlassian's platform, used to hold per-issue job status while a send runs and to stage attachments on their way to Jira. No issue content is kept there.
The write scope is granted with impersonation, which is what lets the app act as you rather than as itself. It is the reason comments and files show your name as the author on every issue — including the large attachments that finish uploading in the background after you have moved on, which is the one place the app is working without you sitting in front of it.
Reading needs no such grant: every read the app makes happens while you are using it, in your own session and under your own Jira permissions. If you cannot see an issue, neither can the app.
Cloud only: Bulk Comments for Jira is built on Atlassian Forge and runs exclusively on Jira Cloud. Jira Server and Jira Data Center are not supported.
Privacy & security
- Data Privacy: DataPingo Privacy Policy
- Security: DataPingo Security Policy
- Data Storage: All app data is stored in Atlassian Forge Storage — no data is sent to or stored on external DataPingo servers
- Media Handling: Images, videos and files move directly to Jira through Atlassian's infrastructure — never through an external server DataPingo operates
- Customer information: We receive customer details only through the Atlassian Marketplace. We do not sell, distribute or share that information.
- GDPR status: Atlassian has approved our declaration that DataPingo is neither a data controller nor a data processor under the GDPR with reference to this app. Verify it yourself on the Privacy & Security tab of the Marketplace listing.
- Compliance: Follows Atlassian security standards and the Forge platform security framework