v4.7.0 — September 21, 2026

New

The Comment step

• A list down the left to move between issues — twenty-five cards is more than one screen. Press a row and that card scrolls into view. Collapsed it is a narrow rail; pin it and it stays open beside the cards. The layout you set is remembered between sessions.
• The details panel follows you — it now describes whichever card you are writing in, instead of staying on the one you opened it from.
• Status moved under the comment box — writing a comment and moving the issue is one thought. In the header it meant travelling back over the editor you had just filled in.
• A request carrying two comments is stacked the way Jira will show it — Jira lists newest first, so the comment that posts last is the one on top afterwards. The card mirrors that, and Move up swaps them.
• Bulk controls that name their own scope — add or delete internal notes across the batch, copy a comment to every card, copy an internal note to every internal note. Each one names the real number it will affect rather than promising “all”, and asks again before overwriting anything you have already typed.
• Clearing keeps the boxes — Clear all comments & status changes names comments and status changes, and a note box is neither. It empties them and leaves them open.

Enhancements

Performance

• The app loads about half the JavaScript it used to — 744 KB down to 356 KB before anything can be drawn.
• Two checks that ran on every keystroke grew with the size of your batch. On twenty-five issues that was felt; both are now flat.

Fixes

An internal note could post to the customer

• If an issue you had selected dropped out of your current search results, the app stopped knowing it was a service request — and a comment sent without that flag posts public. The browser no longer decides this; the server does, for every issue in the send. Measured on Cloud.
• An issue opened from an issue’s own ••• menu never passed through a search, so it arrived with no information about itself: no audience control, and forced internal. It now carries the same details as any other issue.

A send could post everything twice

• A send has twenty-five seconds before Atlassian stops it, and when that happened there was no result at all — so a send that died at issue 18 of 25 left 17 comments in Jira with nothing on screen to say so, and the next press posted all 17 again.
• The app now stops starting new issues with time to spare and answers normally, marking the rest Not sent. A known partial result is safe to retry.
• If the connection drops and nothing comes back, Send is held until you confirm you have checked the issues in Jira — rather than leaving the button armed on a guess.

Reporting that was untrue

• A status change Jira rejected used to draw a green tick and “25 of 25 updated”. It is counted separately now, and Retry deliberately skips those issues, because re-running one would post its comment a second time.
• A stale transition now says the issue moved in Jira after you picked it, rather than claiming a required field is missing.
• JQL mode showed the project, status, assignee and sort controls as applied while the query ignored all four.
• /Divider inserted a divider that posted as nothing.