Bulk Comments for Jira

Release notes

Every released version of Bulk Comments for Jira, newest first — what changed and when.

v4.2.0 — Latest Runs on Atlassian Atlassian Forge Jira Cloud
← Back to the guide

Version History

Release history for Bulk Comments for Jira on the Atlassian Marketplace.

VersionReleasedSummary
4.2.0Aug 6, 2026Licence checks on send, and two reporting fixes
4.1.0Aug 3, 2026Per-ticket status changes, full issue context, and a storage check on send
4.0.0Jul 22, 2026One comment page with per-ticket overrides, 150 MB attachments, and undo
3.7.0Jul 17, 2026A different note per ticket, in-context writing, and parallel posting
3.4.0 – 3.6.0Jul 16, 2026Performance and reliability — faster editor, per-ticket draft autosave
3.3.0Jul 9, 2026Initial public release — one comment to 25 issues, plus copy a comment

Release Notes

v4.2.0 Latest August 6, 2026

The app now checks your site’s licence before it sends. If yours is active — including the free tier and a trial — nothing about this release is visible to you.

  • Licence checked at send — only an expired or cancelled licence is refused, and only for sending. Browsing tickets, writing drafts, copying a comment link and undoing a previous send all keep working, so nothing you have already written is lost and nothing you have already posted becomes unremovable.
  • Free and trial sites are unaffected — a free licence is an active licence. Teams of 10 or fewer, and anyone inside a trial, send exactly as before.
  • Attachments are checked first — the licence is confirmed before any file starts uploading rather than after, so a refused send cannot leave stray attachments behind on a ticket.
  • Sends already running finish — if a licence lapses mid-run, the work in flight completes. A half-posted batch is worse than either outcome.
  • Undo no longer reports a text-only rollback as a failure — undoing a send with no attachments removed the comments correctly but announced an error.
  • Restored drafts say what they dropped — tickets that have since been deleted or moved out of reach are removed from a recovered draft, and named, instead of failing silently at send time.
v4.1.0 August 3, 2026

Status changes move from a side effect to a first-class part of a send, and the size of a batch is now something you can see before it lands.

  • Change status as you comment — move each ticket while you write its comment, chosen from that ticket’s own workflow so you only ever see transitions Jira would accept. A status change counts on its own: a ticket with a new status and no comment is still included in the send.
  • Full ticket context beside the editor — open any ticket and its description, details and attachments sit next to the comment you are writing, along with every comment already on it.
  • Filter by status — narrow the ticket list by status as well as project, in your own workflow’s wording. Done work is hidden by default; one tick brings it back.
  • A storage estimate before every large send — the confirmation now does the arithmetic for you. A file lands once on every ticket, so 150 MB across 9 tickets reads as 1350 MB written into Jira, named before anything posts.
  • A 2 GB ceiling per send — totalled across every ticket in the batch. Anything larger stops before it starts and asks you to split it into smaller batches, rather than failing partway through and leaving some tickets done and some not.
  • Files over 150 MB are refused at attach time, the moment you add them, rather than after you have written the comment.
  • Clear all keeps your selection — it now clears the comments and status changes in place instead of emptying the ticket list and sending you back to the start.
  • The ••• actions menu opens the full app with that ticket already selected, instead of a cut-down compose box.

Undo does not revert a status change. It removes the comments a send posted and the files it uploaded, freeing that storage — but tickets stay where you moved them. Move those back in Jira.

v4.0.0 July 22, 2026

One page to write on, and a way back from a send that went out wrong.

  • One page to write — one comment for every selected ticket, and a different comment for any ticket that needs one, without switching screens.
  • Attachments up to 150 MB each, uploading while you write so they are ready the moment you send.
  • Undo on every screen — removes the comments a send posted and the files it uploaded, freeing that storage again.
  • Send progress now shows upload speed, elapsed time and a Cancel button.
  • Files copied with Copy a comment are recorded under your own name.
v3.7.0 July 17, 2026

The first version where every ticket could say something different.

  • A different note per ticket — write a separate comment for each selected issue.
  • Write or copy in context from an issue’s ••• actions menu and Activity tab.
  • Parallel posting for faster large batches, with a confirmation before sending to 10+ tickets or posting an @mention.
v3.4.0 – v3.6.0 July 16, 2026

Performance and reliability, plus the refreshed in-app icon.

  • Parallel comment posting and faster editor loading.
  • Per-ticket draft autosave, so a half-written batch survives a reload.
v3.3.0 July 9, 2026

Initial public release on the Atlassian Marketplace.

  • Write a comment once and post it to up to 25 Jira issues.
  • Copy an existing comment with its images, videos and file attachments.