-
v1.2.0
released this
2026-07-23 12:44:40 +02:00 | 6 commits to main since this release- E-mail intake (IMAP), optional and off by default: clients can create a
ticket or reply to an existing one just by sending/replying to an e-mail.
Configure any number of mailboxes in the new Admin > Poczta page (SMTP +
IMAP together, replacing the old "E-MAIL" tab), each routed to a specific
subcategory or a whole category (new tickets.category_id column). Replies
are matched to their ticket via the number/checksum already in every
notification subject; autoresponders/bounces are detected and rejected;
"restrict tickets to LDAP" is enforced for e-mail like the guest web form.
Manual "Pobierz teraz" per-mailbox fetch button; dedicated
storage/logs/imap-*.log regardless of the app's log level; mail-icon badges
on e-mail-originated tickets/messages in the operator queue and ticket view. - Operator queue: "select all" checkbox in the table header for every
currently visible ticket under the active filter/tab. - Fixed: scheduled commands (SLA breach check, automation rules, and now IMAP
fetch) always sent notifications through .env's default mailer instead of
the configured SMTP server, because AppServiceProvider's Settings override
used to skip itself for any console command, not just migrate. - Fixed: visiting a ticket that no longer exists (deleted mid-session, or a
stale background refresh) showed a raw 404 instead of redirecting back to
the operator queue / client dashboard. - Docs: README/ARCHITECTURE/CLAUDE/install/wiki updated for all of the above,
including the previously-missing host crontab entry for schedule:run.
Downloads
- E-mail intake (IMAP), optional and off by default: clients can create a