- Shipped
- August 27, 2026 at 8:28 PM UTC
- Author
- Kamo
- Commit
- d0cd3d3
MediaService now emails a reporter whenever their bug or enhancement changes status, but a dispatch applies a status of its own — usually In Progress — through **************** in this JVM, without ever touching MediaService. Left as it was, the one transition that says somebody has actually started work would be the one the reporter never heard about, and a notification stream with a hole in it is one people learn not to trust. Both sides build their variables through com.kamo.z.shared.support. SystemBugStatusEmail, so the two letters are the same letter. The previous status is captured before the dispatch runs: by the time audit.complete has committed in its own REQUIRES_NEW transaction, the row no longer remembers where it came from. The notice goes out whether or not the hand-off to the dev machine confirmed, for the same reason the status is applied either way — the row now says what it says and the reporter can see it, so an email that only matches the screen on the happy path is worse than none. Read and send are separate beans. A @Transactional method invoked on `this` goes around Spring's proxy and runs with no transaction at all, which with no open-in-view means the LAZY reporter.getUser() throws; crossing a bean boundary is what makes the annotation apply. The send then happens outside the transaction so a network round trip never holds a database connection. Every failure path is never be turned into a 500 by an email.