Help Desk
Exception Manager
Professional, branded error dialogs with reference codes & built-in support tickets
Replace Odoo's default technical error pop-ups with a single, polite, on-brand experience. Access errors, validation errors, unhandled tracebacks, raw PostgreSQL constraint violations and session expiry all share the same clean visual language — with copyable error reference codes, an in-app support ticket workflow, and real email notifications — all native to Odoo 17.
Key capabilities
Friendly dialogs, every error family
Access Restricted, Action Required, Invalid Information, Record Not Found and Session Expired each get their own icon and plain-language message, instead of Odoo's raw technical pop-up.
Copyable error reference codes
Unhandled errors show a short reference like ERR-20260709-FC26.
The same code is written to the server log and stamped on any ticket, so
support can correlate instantly.
Admin-only technical details
Regular users see a friendly message. System Administrators keep full tracebacks and technical context behind a "See details" toggle.
Contact Support on every dialog
In-app ticket (zero configuration), a support email, or your own external help desk URL — configurable in one screen, with server-side validation and safe fallback.
Built-in support tickets
Chatter, statuses (New / In Progress / Resolved / Closed), record rules so users only ever see their own tickets, and a top-level Support menu.
Real email notifications
System Administrators are emailed the moment a ticket is submitted; the reporter is emailed the moment it's marked Resolved — through your own Outgoing Mail Server, independent of anyone's notification preference.
Friendly SQL constraint messages
Raw PostgreSQL wording (not-null, unique, foreign key, check violations) is translated to plain language while the technical error stays in the server log.
Fully translatable
Every user-facing string, including the email notifications, is resolved at runtime in the recipient's own language.
See it in action
The same tinted, branded dialog appears wherever an unhandled error happens, with a copyable reference code and a one-click way to reach support — no raw traceback in front of the end user.
One click on Contact Support opens a small pre-filled form (the error reference is carried over automatically); submitting it creates a ticket instantly and confirms it right away — no page reload, no external help desk required.
Finding your way to Support
Beyond the error dialogs, every user gets a dedicated Support menu in the main navigation bar — so raising or checking on a ticket never depends on hitting an error first.
Ticket workflow & email notifications
Every ticket lives in a proper workflow with chatter, statuses and record rules. Reporters see only their own tickets from a dedicated Support menu; administrators manage every ticket and each status change is logged — with a guaranteed email sent for the two moments that matter most: a new ticket coming in, and a ticket being resolved.
The envelope icon next to each administrator update marks a real notification that was emailed out — submission and resolution both trigger a guaranteed email in addition to this in-app trail, each independently switchable under Settings → General Settings → Exception Manager.
The moment a ticket is submitted, every System Administrator with a valid email address receives this notification with the reporter's details and the ticket reference.
Once an administrator marks the ticket Resolved, the original reporter is automatically emailed a confirmation — regardless of their own in-app notification preference.
Administration
System Administrators reach every ticket from a dedicated Support Tickets entry under Settings, review all tickets from all users in one list, and slice them by status, reporter or submission date.
How it works
1
An error happens
The user sees a friendly, branded dialog instead of a raw technical pop-up.
2
Contact Support
One click opens an in-app ticket form (or your configured email / help desk).
3
Administrators are emailed
A real email goes out the moment the ticket is created.
4
Resolve & notify
Work the ticket through its statuses; the reporter is emailed the moment it's resolved.
Technical
Built for Odoo 17 (Community & Enterprise). Depends only on
base, web, base_setup and mail.
No external services required — email notifications use your own
configured Outgoing Mail Server. Security groups (Reporter / System
Administrator) and record rules keep every user scoped to their own tickets.
Licensed under LGPL-3 (free & open source).
Author & support
Developed and maintained by Faridullah Qaderi
FOITECH — Digital Solutions
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
Discuss (mail)
|
| Lines of code | 1210 |
| Technical Name |
foi_base_exception_manager |
| License | LGPL-3 |
| Website | http://faridullahqaderi54@gmail.com |
Please log in to comment on this module