Bulk Comments for Jira

v4.6.0 — September 7, 2026

Jira Service Management and Customer Service Management support: each request gets a reply to the customer, an internal note, or both.

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

Release date: September 7, 2026  ·  Version: 4.6.0

New

Service desks

  • 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

  • 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.

Accessibility

  • 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.

Enhancements

Sending

  • 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.

Appearance

  • Dark mode follows Jira, not your operating system — a dark Jira used to render a white app.

Fixes

Attachments

  • Attachments survive a partial failure — three paths discarded files that had already uploaded, leaving them orphaned in Jira with nothing tracking them.