Help and support

This app can attach files up to 150 MB — attach it directly in Jira on each issue that needs it.

One file is over the per-file ceiling. The limit is per file, not per comment — three 140 MB files are fine, one 160 MB file is not.

Do exactly what the message says: attach that one file to each issue directly in Jira, outside the app, then write the rest of the comment here as usual.

This send is over the 2 GB limit for one send — revise your comments, or send in smaller batches.

The app caps a single send at 2 GB written into Jira in total, counted across every issue in the batch. A file is written once for every issue it lands on, so the total is file size × issue count — a 400 MB video sent to 5 issues writes 2 GB. See Limits. This is separate from the 150 MB per-file ceiling — a batch can breach the total while every individual file is well inside its own limit.

Split the batch. Send half the issues, then the rest — the total resets per send. Nothing was posted when the limit tripped, so there is nothing to clean up first. Remember that a file lands once per issue, so dropping issues from the selection cuts the total faster than shrinking the file does.

Jira did not finish attaching the files in time. Nothing was posted — try fewer issues, or a smaller file.

The upload ran past the time the platform allows. Larger files across more issues multiply: the same file going to 25 issues is 25 uploads.

Send to fewer issues in one pass, or shrink the file. Nothing was posted, so there is nothing to clean up before retrying.

The upload stopped making progress and was abandoned. Nothing was posted — try a smaller file, or fewer issues.

The transfer stalled rather than failed outright, usually a slow or interrupted connection.

Check your connection and retry. Keep the tab open while a large send runs — closing it stops the upload.

The site has exceeded its storage limit  /  Attachment quota exceeded for this instance

This is Jira’s own limit, not the app’s. A file lands once on every issue you send to, so a 100 MB video across 25 issues writes 2.5 GB.

Free space in Jira, or send to fewer issues. The confirmation before a large send shows the total it is about to write, so you can drop issues before anything is posted.

You don’t have permission to comment on the selected issue(s).

One or more selected issues sit in a project where your account cannot add comments.

Remove those issues from the selection, or ask a project admin for the Add Comments permission. The rest of the batch is unaffected.

No permission to add attachments

You can comment on the issue but not attach files to it — these are separate Jira permissions.

Post the comment without the attachment, or ask for the Create Attachments permission on that project.

That status change needs a field this app can’t set — do it in Jira

The transition has a screen attached that requires input — a resolution, an assignee, a custom field.

Move that issue in Jira, where the transition screen can be filled in. Its comment still posts normally from here.

Moved in Jira since you picked it — reload and choose the status change again

Somebody moved the issue between the moment you chose the transition and the moment you sent, so the transition you picked is no longer on the workflow from where the issue now sits.

Reload the app and pick the status change again from where the issue is now. The comment on that issue is unaffected.

n status changes failed — the comments posted, change the status in Jira

Two different things happened to one issue: the comment posted and the transition was refused.

Move those issues in Jira. Retry will not pick them up, and that is deliberate — their comments are already in Jira, so re-running one would post its comment a second time. The rows name the issues, and each links straight to it.

I need to take a send back

There is no undo. A customer reply is emailed the moment it posts, so nothing could reliably take one back.

Delete the comments on the issues in Jira. The results screen lists every issue the send touched, with a link to each one, so you have the record of what to remove. Two things cannot be reversed: an email that has already reached a customer, and a status transition — move those back in Jira yourself. The send guard is what prevents this: before anything posts it names how many customers will be emailed, how many comments post and across how many issues, and — when the send carries files — how much storage it will add.

Add a comment or a status change to at least one issue.

Every selected issue still carries no badge, meaning nothing has been done to it yet, so there is nothing to send.

Open an issue and give it a comment, an attachment or a status change. Any one of the three makes it ready; the footer count tells you how many are.

Maximum 25 issues per bulk post

The selection is over the per-send ceiling.

Send in batches of 25. The tray along the bottom of the Issues step lets you drop issues with the × on each chip.

Some issues succeeded and some did not

Each issue is tracked on its own, so a partial result is normal rather than a broken run. It has two causes: Jira refused the post (failed), or the send ran out of time before that issue was started (not sent — nothing was posted to it).

Use the retry button on the results screen — it reads Retry n failed, Retry n unsent or Send the remaining n depending on what is left. It re-runs only issues where nothing was posted, and leaves everything already delivered alone.

Not sent — the send ran out of time. Nothing was posted to this issue.

A send gets 25 seconds from Atlassian before the run is stopped. The app stops starting new issues with time to spare and answers with what it has.

Nothing was posted to those issues, so retrying is safe — the retry button covers them. If it keeps happening, the batch is heavy rather than broken: send in smaller groups, or attach fewer files per issue.

The send was interrupted, so we don’t know which comments went through

The connection dropped before any result came back, so the app genuinely cannot tell what landed. Some comments may already be in Jira.

Check the issues in Jira before sending again — anything already posted would be posted twice. Send is held until you press I’ve checked — let me send.

This site’s license is no longer active. Bulk Comments is free for teams of 10 or fewer — renew on the Atlassian Marketplace.

Atlassian reports this site’s subscription as expired or cancelled. It is not about your own Jira permissions — sending is unavailable for everyone on the site until it is renewed. On a site of 10 users or fewer this usually means an evaluation ended: the free tier is a subscription of its own, and a trial does not roll into it automatically.

A site admin opens the listing’s Pricing tab and uses Get it now, which starts the subscription — at no cost for 10 users or fewer. Apps → Manage apps in Jira will not help here: it lists what is installed and has no subscribe control. Nothing you have written is lost — drafts survive — and the app re-checks when you come back to the tab, so the same send goes through with nothing to retype.

The send button is greyed out, with “This site’s license is no longer active” beside it.

The same thing, said before you start rather than after. The button is disabled deliberately so you do not pick 25 issues and write 25 comments only to be refused at the end.

Use Renew on Marketplace → beside the message, then return to this tab. If it is still disabled, reload once. Browsing and writing are never blocked; only the send itself is.