.png)
Admin guide
The app has no settings of its own. This is what an administrator controls around it.
Site settings that change what the app can do
Two Jira settings, both under Settings → System → Attachments, are read by the app at run time. Everything else it does is governed by ordinary project permissions, below.
Maximum attachment size
The app asks Jira for your site’s own limit and applies the smallest of three numbers to every file:
| Ceiling | Value | Set by |
|---|---|---|
| Your site’s attachment size | varies | A Jira site admin |
| What the app’s backend can hold | 150 MB | Fixed |
| Forge Object Store, per object | 1 GB | Atlassian |
So an administrator can lower the per-file limit below 150 MB, but raising the site limit above it changes nothing — 150 MB is the app’s own ceiling and stays the binding one on most sites. The limit is checked as a file is dropped in, not after the comment is written, so an oversized file is refused immediately.
Attachments turned off site-wide
If attachments are disabled for the whole site, Jira refuses the upload and the app reports You do not have permission to attach files to that issue. against the affected issues. The comment text still posts — only the files are rejected.
Project permissions
The app acts as you, never as itself. Every comment, attachment and status change is written with your account, so Jira applies exactly the permissions you already have. If Jira would refuse you, it refuses the app — there is no elevated path.
Four project permissions decide what a given person can do, and they are granted per project by a project administrator:
| Permission | Without it |
|---|---|
| Browse Projects | The issue never appears in the list to be picked. |
| Add Comments | That issue is refused at send and the row names the reason. The rest of the batch is unaffected. |
| Create Attachments | The comment posts; the files on it do not. |
| Transition Issues | The comment posts and the status change is refused — reported separately, never as a success. |
Because permissions are per project, a batch spanning several projects can partly succeed. Every issue reports its own outcome rather than the batch sharing one.
Installation and access
Bulk Comments is an Atlassian Forge app. It installs site-wide and needs a Jira site administrator, because Forge apps cannot be installed per project. Once installed it appears for everyone who can reach the projects they want to comment on — there is no per-user enablement step.
It requests four scopes, and nothing else:
- read:jira-work — to list the issues you can already see
- write:jira-work — to post the comments, attachments and status changes
- read:jira-user — to show who an issue is assigned to
- storage:app — to hold drafts and staged files between steps
The app runs entirely on Atlassian infrastructure and carries the Runs on Atlassian badge, so no data leaves your Jira site and there is no external server to allow-list. Uninstalling from Apps → Manage apps deletes everything it stored; comments already posted stay on their issues as ordinary Jira comments.
The step-by-step install is under Get started → Installation.