Bulk Comments for Jira icon
Jira App Runs on Atlassian

Bulk Comments for Jira

Write a different comment for each Jira ticket and change the ticket status — up to 25 at once, on one page. You can also write a single comment and send it to all of them. Copy an existing comment by grabbing the comment link and posting the comment across with full fidelity (images, videos, files included).

Install on Atlassian Marketplace View Documentation

One for all, or its own for any

One comment for all 3 tickets Click to write — every ticket gets this unless given its own
Or give a ticket its ownClear all
PAY-412 Add Stripe webhook retry handlingEric Huang · 4 media To DoNot written
PAY-418 Refund flow returns 500 on partialsUnassigned · 1 media In ProgressNot written
PAY-423 Sandbox keys rotate on every deployEric Huang · 2 media To DoNot written
PAY-412 To Do
Add Stripe webhook retry handling
Description
Details
Attachments4
Set PAY-412 from To Do to Set status In ProgressIn ReviewDone
PAY-412’s comment
Normal text@ to mention
rollout-check.png3.1 MB · uploaded
All comments · 4FullSimple
One comment for all 3 tickets Click to paste a comment link — every ticket gets a copy
These 3 get the copyClear all
PAY-412 Add Stripe webhook retry handlingEric Huang · 4 media To DoWaiting for a link
PAY-418 Refund flow returns 500 on partialsUnassigned · 1 media In ProgressWaiting for a link
PAY-423 Sandbox keys rotate on every deployEric Huang · 2 media To DoWaiting for a link
Source comment
Copy an existing comment
Every selected ticket gets a copy — text, images, video and files included.
How to copy a comment link
Paste the comment link
your-site.atlassian.net/browse/PAY-412?focusedCommentId=10842
Source · 4 mediaFullSimple
3 ready · 2 moves · files to 150 MB

Highlights

A whole project. Or several. All on one page.

The part everyone quietly dreads — updating multiple tickets one at a time. Ticket after ticket, project after project — let's do all that in a single send.

WRITE · PER-TICKET One comment for all 3 tickets every ticket gets this unless given its own OR GIVE A TICKET ITS OWN TP3-19 Document API endpoints TO DO Ready — own → DONE DTB-5 Rate limiting on the API TO DO Ready — own DTB-2 Upload progress stalls IN PROGRESS Ready — own TP3-19 TO DO Document API endpoints Description Details Attachments 9 Set TP3-19 to Done TP3-19’s comment B I U @ to mention Swagger spec published — all endpoints documented. api-spec.png 3.1 MB · uploaded

Write · Per-ticket

A different comment on every ticket

Working through a whole project? Or working across multiple projects? Write one comment for every ticket, then click any single ticket to write it a different comment — formatting, @mentions and all — without leaving the page. Everything posts in one send.

WRITE A COMMENT ALL 25 TICKETS One comment for all 25 tickets Every ticket gets this — unless you open one and give it its own. B I U @ to mention Deploying the hotfix now — validating on staging. staging-green.png 2.4 MB Post to 25 tickets ×25 TICKETS ENG-142 ENG-158 OPS-31 DES-19 ENG-160 OPS-34 + 19 more

Write · One for all

Write it once, post it twenty-five times

Write the comment once — bold, lists, quotes, tables, @mentions, and any images, videos or files you need at up to 150 MB each. Every ticket you picked gets it, up to 25 of them: same text, same formatting, same attachments, in a single send.

COPY A COMMENT SOURCE COMMENT 2 images 1 video 1 file ≈ 34.2 MB EXACT COPY 2 images 1 video 1 file ≈ 34.2 MB COPIED EXACTLY Text Formatting Images Video Files

Copy a comment

Copy a comment, media and all

Find the comment you want in Jira, copy its link, and paste it in. It goes out to up to 25 tickets as a new comment that matches the original exactly — text, formatting, images, video and files. Media moves directly between tickets, so nothing is re-uploaded and nothing is quietly left behind.

How It Works

Two ways in. One page to write.

Three steps: pick your tickets, write the comment, send. Open it from the sidebar, any ticket's ••• menu, or the Activity panel — in light or dark, matched to Jira.

02
Comment
Step 1, Tickets: search or paste an issue key, switch to JQL, filter by project and status, and select up to 25 issues in one pass. The tray along the bottom lists every selected ticket.
Step 2, Write a comment: the ticket list on the left shows each issue with its status and whether its comment is ready, and the panel on the right holds the open ticket's description, details, attachments, its status change and its own comment editor.
Step 2, one shared comment: the panel on the right writes a single comment that every selected ticket receives, with an image attached, while the list on the left shows each ticket marked ready.
Step 2, Copy a comment: paste the link to an existing comment and the panel confirms it, showing the source author, what the comment contains and how much storage the copy will use. Every selected ticket is marked to receive it.
Step 3, Send: the run summary counts what was updated, sending and failed, lists each ticket with the status change it received, and offers a single undo for the whole send.

Three ways to write it, all on the same page. Mix them freely — a shared comment for most tickets and its own for a few is one send, not two.

Search by keyword or issue key, filter by project and status, or use advanced JQL. Select up to 25 tickets in one pass — always the first step.

Click any ticket and write it something of its own — formatting, @mentions and files included. Blank ones are skipped.

Write once into the shared comment and every selected ticket gets it — same text, same attachments.

Paste the link to a comment that already exists and copy it across exactly as-is — images, video and files included.

Per-ticket delivery live — Delivered, Sending, Failed — with a link to each ticket, one-click retry on failures, and undo for the whole send.

Features

Everything you need to comment at scale

Built on Atlassian Forge — no external servers, no data leaving your Jira instance.

A Different Comment on Every Ticket

Click any ticket and write it something of its own, with its description, details and attachments open beside you — so you can see what you are commenting on. Tickets you leave blank are skipped.

Change the Status as You Comment

Give each ticket its own status change in the same pass — To Do to In Review on one, In Progress to Done on the next. Statuses come from each ticket’s own workflow, and it is optional per ticket.

One Comment for All 25

Write once into the shared comment and every selected ticket gets it — same text, same formatting, same attachments. Mix the two freely: a shared note on most tickets and its own on a few is still one send.

Copy a Comment Exactly, Media Included

Paste the link to a comment that already exists and it posts to up to 25 tickets as a new comment matching the original — text, formatting, images, video and files. Media moves between tickets without re-uploading.

Live Delivery, Retry and Undo

Watch each ticket land — Delivered, Sending, Failed — with a link to every one, one-click retry on anything that fails, and a single undo that removes the comments and the files they uploaded.

Secure & Atlassian-Approved

Built on Atlassian Forge — no external servers, no third-party data transfers. All data stays inside Atlassian’s infrastructure.

150 MB
Per file

The ceiling is per file, not per comment — one comment can carry as many as you need. Anything larger is refused the moment you attach it, not after you have written the comment. If your Jira site sets a lower limit, that one wins.

2 GB
Per send

The total across every ticket in one batch, added together rather than multiplied out. Go over and the send stops before it starts and asks you to work in smaller batches — rather than failing halfway and leaving some tickets done and some not.

Shown first
Storage arithmetic

A file lands once on every ticket you send to, so 150 MB across 9 tickets writes 1350 MB into Jira. The confirmation does that multiplication and names the figure before anything posts — and undo gives the storage back.

Pricing

Simple, usage-based pricing

Free for teams up to 10 users. Enter your team size to see your estimate.

Estimate your cost

Best for single Jira instance

Free for teams up to 10 users — no credit card needed.

Monthly Estimate

Adjust the slider to see
your live cost estimate.

FAQ

Frequently Asked Questions

Up to 25 issues per send — whether you are writing one comment for all of them, a different comment on each, or copying one that already exists. Status changes ride along in the same send, so 25 tickets can be commented on and moved in one pass.
Write a comment is for new text. Write one comment and send it to all 25 tickets, or give every ticket a different one — and you can mix the two, so a shared note on most tickets and its own on a few is still a single send. The full Jira editor is there: formatting, lists, tables, @mentions, and any images, video or files you attach yourself.

Copy a comment starts from a comment that already exists. Copy that comment’s link in Jira, paste it in, and it posts to up to 25 tickets as a new comment matching the original exactly — media included.
Yes. Write one comment for every selected ticket, then click any ticket in the list to write it a different comment instead. The list shows at a glance which tickets share the comment and which have their own, and only tickets with a comment are posted.
Yes. Paste the link to a comment that has attachments and the media moves directly between tickets — no downloading, no re-uploading. Each file can be up to 150 MB, or your site’s own Jira attachment limit if that is lower, and a comment can carry as many files as you need — the ceiling is per file, not per comment. Bear in mind attachments are issue-scoped in Jira, so a file lands once on every ticket you send to.
Yes — 2 GB in total for a single send, 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 goes. That is separate from the 150 MB per-file ceiling, so a batch can breach the total while every individual file sits well inside its own limit. Go over and nothing is posted — the send stops before it starts and asks you to revise the comments or work in smaller batches, rather than failing partway through and leaving some tickets done and some not. Splitting works because the total resets per send. Before any large send the app also shows the storage arithmetic first, so you see what it is about to write into Jira before it writes it.
Yes, and each ticket can move somewhere different in the same send — one to In Review, the next to Done, and others left where they are. The options come from each ticket’s own workflow, so you only ever see transitions Jira would actually allow. A ticket can take a status change on its own, without a comment. One thing to know: undo removes the comments and the files they uploaded, but it does not put statuses back — move those in Jira.
Yes. Bulk Comments for Jira is built on the Atlassian Forge platform, so file bytes and comment data move directly between Jira tickets through Atlassian's own infrastructure — never through an external server we operate. There are no third-party API calls and no data stored outside your Jira instance.
Three places. The left sidebar — the Bulk Comments for Jira page, the full app. Any ticket’s ••• menu — opens the app with that ticket already selected, so you carry on picking the rest. The “Bulk Comments” tab in an issue’s Activity panel — sits under the comment history and copies a comment from that ticket to others without leaving the page.

Support & Contact

Questions? We're here.

Reach us at support@datapingo.com — we typically respond within one business day.

Browse Documentation Open Support Ticket

Start bulk commenting on Jira issues in minutes.

Install from the Atlassian Marketplace — built on Forge, with all your data staying inside Jira.

Install on Atlassian Marketplace