Auto Assignment strategy, and open an assigned conversation automatically

Featurekamo-internal
Shipped
August 10, 2026 at 7:17 PM UTC
Author
kamo
Commit
f2538d1

Topics settings gains the fourth strategy. The list rows and the edit dialog share the same label, and the key shipped to kamo-translation-dictionary first — messages/ is gitignored here and next-intl throws on a key missing from en.json, so landing this ahead of the dictionary would ship a build whose page crashes. AssignedTicketOpener raises the ticket window the moment work becomes this member's, and again on sign-in for anything assigned while they were away. Both paths run one fetch of /assigned-unopened, so "it arrived while I was here" and "it arrived while I was gone" are one case rather than two mechanisms that have to agree — the ASSIGNED push is core NATS and is simply lost if nobody is listening, which is why it is treated as a hint and the server holds the record. Not gated on availability or on the accept-popup's rules: this is not an offer that can be decoderd, the work is already assigned. The popup exists for the opposite situation. Unlike the NEW_TICKET auto-open removed in addd9036, ASSIGNED only ever reaches the one agent it concerns, so it cannot open a window on every screen in the org.

All changes

Like what you see shipping?

Every one of these updates lands in your workspace automatically. Start free and watch it grow week after week.

Start Free ForeverView Pricing