- Ya
- 27 Agosti 2026, 20:16 UTC
- Mwandishi
- Kamo
- Ahadi ya
- 7b0ea8c
A member who files a bug or an enhancement had no way to learn what happened to it short of opening the tab and looking. This adds the template that tells them, and the one builder both senders use. SystemBugStatusEmail is deliberately static and free of Spring, because two services move a status: MediaService when an operator picks one in the triage drawer, SecurityService when Send To AI applies one as part of dispatching. A reporter told about one kind of move and not the other learns not to trust the emails at all, so the two have to produce the same letter — and the only way to guarantee that is for them to call the same function. The letter names both halves of the transition, not just where the report landed: told only the new status, a reporter cannot tell an advance from a reversal. It also names who moved it, stamps the time in the reporter's own timezone (a bare server LocalDateTime is UTC with no offset, so rendering it as-is is an hour that is wrong for almost everybody), and carries a per-status sentence that differs for a defect and for a request — "won't fix" on an idea answers a question nobody asked, which is why the enum's own label was renamed to "Won't Fix / Denied". TemplateRenderer cannot branch and does not escape, so everything conditional is pre-rendered here: the status colours (the same ramp the console draws its chips with), the Awaiting Info callout, and the call-to-action, which collapses cleanly rather than shipping a button pointing at "https://internal./…" when an org has no resolvable domain. Values a person typed ship twice — tag-stripped for the subject, HTML-escaped for the body — the convention ChatEmailNoticeService set. The deep link names the report rather than the tab on purpose. The tab's status filter defaults to New and this email is by definition about a report that has just stopped being New, so a link to the bare tab would put an empty list in front of somebody who was told their report moved.