Bulk Comments for Jira

FAQ

The questions that come up before, during and after a batch — and where the full answer lives.

v4.8.0 — Latest Runs on Atlassian Atlassian Forge Jira Cloud

Setting it up

Is there anything to configure after installing?

No. The app has no settings screen and adds no admin page to Jira. What it is allowed to do is decided entirely by the Jira permissions you already have — see the Admin guide.

Who can use it once it is installed?

Everyone on the site. Forge apps install site-wide, so there is no per-project or per-user enablement step. What each person can actually comment on is still decided by their own project permissions.

Can I restrict it to certain projects?

Not from inside the app, because there is nothing to configure. It acts as you, so it can only reach issues you can already reach. Jira’s own project permissions are the control: without Add Comments on a project, the app is refused there too.

Will it slow my Jira site down?

It runs on Atlassian’s own infrastructure and only does anything while you have it open. It adds no custom fields, no workflow rules and no background jobs to your site — it contributes two menu entries and nothing else.

Does it work on Jira Server or Data Center?

No. It is built on Atlassian Forge, which is Cloud only.

Which Jira products does it work with?

Jira, Jira Service Management, Customer Service Management and Jira Product Discovery. On a service project you also get a choice of audience — see Service Management and Customer Management.

Limits and sending

How many issues can I comment on at once?

Twenty-five per send. The tray on the Select step stops you picking a twenty-sixth. A service-project request can carry two comments, so a full batch is up to 50 comments across 25 issues.

What if I need more than 25?

Send in batches. Filter down to the first 25, send them, press Done and pick the next set. Anything you wrote on issues you have not sent yet is kept.

How big can an attachment be?

150 MB per file, and one comment can carry as many files as you like. If your Jira site sets a lower attachment limit, that one wins — the app applies whichever is smaller.

Why is my send bigger than the files I attached?

Because a file is written once for every issue it lands on. 150 MB across nine issues writes 1,350 MB into Jira. The 2 GB per-send ceiling is counted that way, and the confirmation names the real figure before anything posts — see Limits.

Can I undo a send?

No. There is no undo; the confirmation before sending replaces it. A customer reply in particular cannot be recalled once the customer has been emailed.

Licensing and purchasing

What does it cost?

Free for teams of 10 users or fewer. Above that it is billed through the Atlassian Marketplace on graduated tiers — the pricing calculator on the product page shows the current rate for your user count.

Do I need a DataPingo account?

No. Billing is Atlassian’s and lands on your existing Atlassian invoice. There is no separate account to create and no payment detail to enter with us — the app never sees one.

Is the free tier a trial?

No. Teams of 10 users or fewer are free on an ongoing basis, not for a limited period.

What happens if the subscription lapses?

The app tells you before you have done any work — a notice on the compose screen, with a link to the place you can renew. Comments already posted are unaffected; they are ordinary Jira comments.

Privacy and security

Where does my data go?

Nowhere outside Atlassian. The app runs entirely on Atlassian infrastructure with no external egress declared, which is what the Runs on Atlassian badge certifies. Nothing reaches a DataPingo server, and there is no endpoint to allow-list.

What permissions does it ask for?

Four, and nothing else: read and write Jira work items, read Jira user profiles, and app storage. See the Admin guide for what each one is for.

Who appears as the author of the comments?

You do. Every write uses impersonation, so comments, attachments and status changes are recorded under your own account rather than the app’s.

Do you store my comments?

Only while you are writing them. Drafts and staged files sit in Atlassian Forge storage so you can leave and come back; nothing is retained once Jira has it. The app keeps no user records of its own.

What happens when I uninstall?

Everything the app stored is deleted. Comments already posted stay on their issues as ordinary Jira comments — nothing is removed from Jira.