Skip to main content

Tickessa 0.16.0

Version 0.16.0 improves safe email handling and highlights unanswered customer requests. The new automatic receipt confirmation remains disabled by default for every project.

New​

  • Reply recipients can be reviewed and changed per ticket. Forwarded messages with ambiguous addresses block sending until confirmed.
  • Project names and colours can be edited with revision protection.
  • Projects can enable a fixed, language-specific receipt confirmation. At most one delivery attempt is reserved for each new accepted email ticket.
  • Spam, quarantined mail, bounces, automatic replies, support addresses, historical imports and ambiguous recipients receive no confirmation.
  • Unanswered tickets show a labelled warning after a project-specific number of UTC calendar days and appear in a dedicated queue.
  • Only a successfully delivered substantive reply ends the deadline. Receipts, notes, drafts and failed deliveries do not count.

Update​

Migrations 031 and 032 add reply-recipient data, project revisions, receipt-confirmation records and deadline settings. Existing projects send no receipt confirmation after the update until an administrator explicitly enables it.

Update the frontend, backend and migrations together. A technical update does not publish or automatically activate any production sending feature.

Validation​

Validation covered the app and handbook builds, typechecking, parser and regression tests, repeatable MariaDB migrations, and successful and ambiguous TLS SMTP delivery. An ambiguous result stays recorded and is never retried blindly.

See Languages and email templates and Replies and internal notes.

Last updated on