DOCUMENTATION
.png)
Troubleshooting
The messages the app can show you, what each one means, and what to do about it.
Comment links
These come up in Copy a comment, where the app needs a link that points at a specific comment rather than at the issue holding it.
That link is missing a ticket key and focusedCommentId. Use the comment’s ⋯ menu → “Copy link”.
You pasted a plain issue link. …/browse/KAN-6 points at the ticket; the app needs the one that points at a comment on it.
In Jira, hover the comment you want, open its ⋯ menu and choose Copy link. The result carries ?focusedCommentId= on the end — that fragment is what identifies the comment.
You don’t have permission to view that source comment.
The link is valid but the comment sits on a project or an issue-security level your account cannot see.
Open the link in Jira first. If it does not load for you there, it will not load here — ask whoever owns that project for access, or copy from a comment you can see.
The source comment has no readable body.
The comment exists but the app could not parse its content — usually a comment made entirely of an unsupported macro or embed.
Copy a different comment, or write a new one in Write a comment and attach the media yourself.
Files and uploads
Attachments are the slowest and most failure-prone part of a send, so most of the guardrails live here.
This app can attach files up to 150 MB — attach it to one ticket in Jira directly, then use Copy a comment to put it on the rest.
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: put the big file on a single ticket in Jira, then copy that comment across. The copy path moves media between tickets without re-uploading it, so the size ceiling does not apply.
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 ticket in the batch. Tickets are added together, not multiplied out: 700 MB on one, 1 GB on another and 300 MB on a third comes to exactly 2 GB and still sends. 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 tickets, then the rest — the total resets per send. Nothing was posted when the limit tripped, so there is nothing to undo first. Remember that a file lands once per ticket, so dropping tickets 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 tickets, or a smaller file.
The upload ran past the time the platform allows. Larger files across more tickets multiply: the same file going to 25 tickets is 25 uploads.
Send to fewer tickets 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 tickets.
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 ticket you send to, so a 100 MB video across 25 tickets writes 2.5 GB.
Free space in Jira, or send to fewer tickets. The confirmation before a large send shows the total it is about to write — and Undo gives that storage back.
Permissions
The app acts as you. If Jira would refuse you, it refuses the app.
You don’t have permission to comment on the selected ticket(s).
One or more selected tickets sit in a project where your account cannot add comments.
Remove those tickets 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 ticket 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.
Status changes
Transitions come from each ticket’s own workflow, so what is available differs per ticket.
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 ticket in Jira, where the transition screen can be filled in. Its comment still posts normally from here.
A status did not change back after Undo
This is intended. Undo removes the comments a send posted and the files it uploaded; it does not move tickets back.
Move them back in Jira. The results screen lists every transition the send applied, so you have the record of what to reverse.
Sending
What the footer counts and what stops a send from starting.
Add a comment or a status change to at least one ticket.
Every selected ticket still reads Not written, so there is nothing to send.
Open a ticket 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 tickets per bulk post / Maximum 25 tickets per copy
The selection is over the per-send ceiling.
Send in batches of 25. The tray along the bottom of the Tickets step lets you drop tickets with the × on each chip.
Some tickets succeeded and some failed
Tickets are posted in parallel and each is tracked on its own, so a partial failure is normal rather than a broken run.
Use Retry n failed on the results screen. It re-runs only the failures and leaves everything already delivered alone.