.png)
Limits
The hard numbers, and the arithmetic behind them.
Limits
Three numbers govern how much one send can carry. They are independent of each other, so a batch can sit comfortably inside two of them and still be refused by the third.
| Limit | Value | Counted how |
|---|---|---|
| Issues per send | 25 | Per send. The tray on the Select step stops you selecting a 26th. |
| Comments per send | 50 | 25 issues, and a service-project request can carry two — an internal note and a reply to the customer. The issue ceiling is what is capped; the comment count follows from it. |
| Size per file | 150 MB | Per file — not per comment. One comment can carry as many files as you like, each up to 150 MB. |
| Total per send | 2 GB | Added together across every issue in the batch, after multiplying each file by the issues it lands on. |
Why the total is bigger than it looks
Attachments in Jira belong to an issue, not to a comment, so a file you send to 9 issues is written 9 times. The figure that counts against the 2 GB ceiling is therefore file size × issue count, not the size of what you attached.
A worked example: four 120 MB videos is 480 MB in the editor, and every file is well inside the 150 MB per-file limit. Send that to 5 issues and Jira receives 2400 MB — over the ceiling, and the send is refused. Send it to 4 issues instead and it is 1920 MB, which goes.
The send guard shows the arithmetic before a heavy send posts. Once a comment carries 50 MB or more of files — or the batch would write 250 MB or more into Jira — the send guard stops and names the figure: “Keep this tab open. This send adds 1350 MB to Jira (150 MB × 9 issues). Make sure you have room for 1350 MB.” You are acknowledging two things when you confirm: that the comment carries files this large, and that your Jira site has the storage for the multiplied total. Under both thresholds the send simply goes.
Nothing is posted when a limit trips. A send over 2 GB stops before it starts, so you are never left with some issues done and some not. Split across two sends and the total resets — the ceiling is per send. An oversized file is refused when you attach it.
If your Jira site sets a lower attachment limit than 150 MB, that one wins — the app reads your site’s real limit and checks against it. Jira’s own instance-wide storage quota is separate again and is not something the app can see; if you hit that, see Files and uploads in Troubleshooting.