Repository navigation
Radd 0.44.1
v0.44.1
5 changes · 1 Bugfix, 4 New Features.
Bugfix
- RADD-972 Automation notifications carry no item ref, so no email line can link the issue they're about
automations/engine.pywritespayload={"message", "rule"}on an AUTOMATION notification while settingitem_idon the row — the payload carries no item key or title. Every renderer that composes a line from the payload (the digest, and any per-event email) can therefore not link the issue: RADD-967 made it degrade…
1e62183d
New Feature
- RADD-994 The routing trace answers "why didn't my rule fire?" with silence: disabled and not-reached rules, the hidden None-of-these, and a clipped detail
Live verification of RADD-989 on v0.30.0 (scenario passed — DEV/ITSUP/DESK by verdict, errored renders distinctly). What would still confuse an admin, found by using it:
2fe530b3 - RADD-982 The lifecycle ends in silence: a resolved notification to the ticket's contacts, out of the box
(audit finding #2)
35dffd32 - RADD-984 mail.sent / mail.failed appear in the item's History, so "did the customer get my reply?" has an answer
(audit finding #4)
cf26ee46 - RADD-985 List-Unsubscribe and a preferences link: every notification email says how to stop it
(audit finding #7, deliverability half)
255a3b6b
Changes from v0.44.0 to v0.44.1.