Bulk Comments for Jira icon

Bulk Comments for Jira

Jira App Runs on Atlassian

Comment on 25 issues at once

Select up to 25 Jira issues and see it all in one page then write comments for each one. Works with every Jira product.

Highlights

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

Updating issues one at a time is the part everyone quietly dreads. Do the whole batch in one send.

PER-ISSUE COMMENTS ISSUES ITS OWN COMMENT DTB-1 Ready DTB-6 Ready PAY-412 Ready

Per-issue comments

A different comment on each issue

Every issue you pick becomes its own card with its own comment box — ready to type into, nothing to open first.

ONE REQUEST, TWO AUDIENCES SUP-241 SSO login fails for contractors Internal Reply to customer Reply to customer posted last · shows on top Internal note posted first THE CUSTOMER Lands on the portal and arrives in their inbox. THE AGENT VIEW Only your team ever reads it. Nothing leaves Jira.

Service projects

Internal notes or reply to customer

On a Service Management or Customer Service request, every comment is an internal note or a reply that reaches the customer — and one send can carry both.

STATUS & CONTEXT ON THE CARDBESIDE IT, READ-ONLY PAY-412 Details Ready STATUS To Do In Progress In Review Done PAY-412 DESCRIPTIONATTACHMENTSCOMMENT HISTORY Assignee Labels Sprint Reply Internal

Issue Details and Status

Read the whole issue at a glance

Details opens the issue’s description, fields and comment history beside your card. Set its status right there — one to In Review, the next to Done.

150 MBPer file, not per comment — one comment can carry as many as you need.
Never twiceRetry re-runs only what didn’t post. A batch over 2 GB stops before it starts.
Light & darkMatched to your Jira theme, so it reads like part of Jira.
Runs on AtlassianBuilt on Forge — no external servers, no data leaving Jira.
Every limit, and what happens at each →

How It Works

Select, comment, send.

All on one page — open it from the sidebar or any issue’s ••• menu.

Step 1, Select: search by keyword or issue key, or switch to JQL. Filter by status, scope to just the issues assigned to you, sort, or select everything visible. Nothing is picked yet — the counter along the bottom reads 0 of 25, and Next: comment stays disabled until you choose something.
Step 2, Comment: a list of every issue in the batch runs down the left, the cards sit in the middle — each with its own comment editor and, under the box, its own status control — and on the right a read-only detail panel follows whichever one is open, showing that issue’s description, fields and comment history.
Step 3, Send: the heading Comments posted, eight of eight updated in one second, with counters for Updated, Sending and Failed. Each issue is listed with the audience its comment reached — two of them badged INTERNAL and SENT TO CUSTOMER — and a link to the comment, above a Done button.

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 a 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

Yes — always. Every issue is its own card with its own comment box, ready to type into. Leave one blank and it is skipped. See the user guide.
Yes. Write it once on any card, then choose Copy this comment to n issues from that card’s ••• menu. Every other card gets a copy, not a link, so you can still reword the ones that need it before you send. See it used for incident and release updates.
Up to 25 per send, each with its own comment and its own status change.
All of them — Jira, Jira Service Management, Customer Service Management and Jira Product Discovery. You can mix them in one send, and the app uses your product’s own word: issues in Jira, requests on a service project, ideas in Product Discovery. How it works across every Jira product.
Yes. On a Jira Service Management or Customer Service Management request, every comment is explicitly an internal note, seen only by agents, or a reply to the customer, which reaches them and emails them. The choice is made per request, so one send can answer three customers and leave private notes on two others. Replies and internal notes, in detail.
Yes. Built on Atlassian Forge — everything moves through Atlassian’s own infrastructure, never a server we run. Privacy & security.

Twenty-one answers in the documentation FAQ →

Start bulk commenting on Jira issues in minutes.

Questions? Email support@datapingo.com or open a support requestWe typically reply within one business day.