Release notes

Bulk Comments now works across every Jira product. On a service desk that meant answering a question the app never used to ask: who is allowed to read this comment. An evaluation churned on exactly that — “Does not work with JSM tickets.”

• Service desks are supported, and every comment states its audience — on Jira Service Management and Customer Service Management, each request carries an explicit choice: Internal note, seen only by agents, or Reply to customer, which reaches the customer and emails them. The choice is per request, so one send can answer three customers and leave two notes for the team.
• A request can carry both at once — the reply the customer reads and the note the team keeps are never the same sentence. Write them separately on the same card and they post together, in order, as one ticket’s work.
• A customer reply cannot be taken back — so before anything posts, the confirmation names exactly how many customers the send will reach. That number is the last thing you see before it goes.
• Jira Product Discovery is supported, and the app uses your product’s word — ideas in JPD, requests on a service desk, issues everywhere else. The noun follows what you selected.
• Undo has been removed — it could not honestly cover a service desk, because a customer email is already sent by the time you press it. An undo that works on four products out of five is worse than no undo, because it teaches you to rely on it. The confirmation before sending replaces it.
• Keyboard and screen-reader support throughout — around thirty controls responded only to a mouse press and could not be reached by keyboard at all. All of them are now reachable and operable.
• Dark mode follows Jira, not your operating system — a dark Jira used to render a white app.
• Attachments survive a partial failure — three paths discarded files that had already uploaded, leaving them orphaned in Jira with nothing tracking them.

A follow-up to 4.4.0 the same day. Rewording the expired-license notice had taken the renewal link out of one place that has no button beside it to make up for it.

• The blocked-send message names the way out — when a send is refused, the message is returned on its own with no button next to it, so it has to carry the instruction itself. It now reads: “This site’s license is no longer active. Bulk Comments is free for teams of 10 or fewer — renew on the Atlassian Marketplace.” The shorter notice on the compose screen is unchanged, because a Renew on Marketplace button sits beside it.
• “License” is spelled the American way — on-screen text only, matching Atlassian’s own spelling.

The notice shown when a site’s subscription has lapsed used to send you to a page where you could not subscribe. Superseded the same day by 4.5.0.

• Renewal opens the Pricing tab — Renew on Marketplace used to open the listing’s Overview page, whose only button is Try it free. A site that has already used its evaluation cannot start a second one, so that button failed for exactly the person being shown the notice. It now opens Pricing, where Get it now creates the subscription.
• The free tier is named — 10 users or fewer costs nothing, but a trial does not roll into the free tier by itself and nothing said so. The wording now matches Bulk Page Cloner, so both apps read the same.
• A one-ticket send reads as one — sending a single comment reported “Comments posted.” It now says Comment posted, and likewise Ticket updated and Status change applied for a single ticket.

Every ticket is now one card, start to finish — its own comment, its own attachments, its own status control, and its full detail a click away. Two long-standing modes are retired to make room for it.

• One flow, not three — Copy a comment and one comment for all are retired. Every ticket always gets its own comment, its own attachments and its own status control, whether you are commenting on one ticket or twenty-five.
• Two ways in, not three — the issue Activity panel’s Bulk Comments tab is gone. Open the app from the global page, or from an issue’s ••• actions menu.
• A ticket’s full detail is always there — click a ticket’s title and its description, fields, attachments and comment history open beside the editor, fully expanded. No settings to turn on first — the separate panel-settings menu is gone.
• Video and images play inline — a video attached to a comment, or already on the ticket, now plays right there with a thumbnail before you click; images open full-size in the app. Both used to only link out to Jira.
• Faster on a heavily-commented ticket — a ticket’s comment text, images and video now load together in one request instead of one call per comment.
• Status colours match your workflow — the ticket picker now colours a status chip by its underlying category rather than its name, so a status your team renamed (“Shipped” instead of “Done”) always shows the right colour.

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

• License checked at send — only an expired or cancelled license 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 license is an active license. Teams of 10 or fewer, and anyone inside a trial, send exactly as before.
• Attachments are checked first — the license 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 license 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.

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.

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.

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.

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.

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.