A custom module on Odoo Enterprise, separate from Odoo's standard Helpdesk app, with its own menus, stages and security groups
Replaces spreadsheets and disconnected tools with one database where tickets, problems, changes and assets are linked
Requires Odoo Enterprise
Ticket lifecycle
From first request to lessons learned
Six connected steps take work from intake to review, all in one database.
1
Step 1: Ticket intake
Requests and incidents raised by portal, email or direct entry, with auto-generated references, priority from an impact-by-urgency matrix, and an SLA matched automatically.
2
Step 2: Assignment and resolution
Tickets routed to teams by manual, round-robin or balanced assignment; Kanban pipeline; On Hold pauses the SLA clock.
3
Step 3: Problem management
Recurring incidents raised as problems with a root-cause pipeline.
4
Step 4: Known errors and knowledge base
A documented workaround creates a knowledge-base article linked to the problem.
5
Step 5: Change and CAB approval
Standard, normal and emergency changes. Higher-risk changes require CAB approval before implementation.
6
Step 6: Post-implementation review
Outcome recorded (successful, partial, failed, rolled back) and linked to the originating problem and tickets.
ITIL is a trademark of its owner.
Core components
What is in the module
Work the queue
Where agents spend their day.
Dashboard
Live KPIs (open, breached, unassigned)
Kanban, list, pivot and graph views
Drill-down from tiles
Tickets
Incidents and service requests with separate references
Priority computed from impact and urgency
Links to problems, changes and assets
SLA policies
Separate response and resolution targets
On track / at risk / breached status
Escalation contacts on breach
Business-hours calculation
Fix causes, manage change
Go beyond the single ticket.
Problems & known errors
Root-cause pipeline
Workaround and permanent fix records
Create a change from the fix
Changes & CAB
Standard, normal, emergency types
Risk-driven CAB requirement
Implementation, rollback, test and communication plans
Knowledge base
Categories and visibility levels (draft, internal, portal)
Voting
Assets and insight
Know what you run and how you are doing.
Assets / CMDB
Configuration item types incl. hardware, VM, business service
Parent/child and depends-on relationships
Warranty status
Reports
SLA compliance, volume trends, category breakdown, team performance pivot
Want to see the ITSM module in action?
Talk to our team about your IT service processes and how they would map to Odoo.
Customer self-service portal to raise and track tickets
Chatter and audit trail on every record
Customer satisfaction (CSAT) ratings
Saved filters and group-by options
Security and governance
Three roles keep responsibilities clear
Agent
Works on records, with read-only access to configuration.
Manager
Full access, including configuration.
CAB Member
Approves changes only.
Language
Language support
Arabic interface support.
How we implement this
Deployed in stages, typically starting with tickets, SLAs and knowledge base, then changes and CMDB. Steps: discovery, design, migrate and build, training, go-live and support.
No. It is a separate ITSM application on Odoo Enterprise with its own menus, stages and security groups. It can run alongside the standard Helpdesk app.
Do we need Odoo Enterprise?
Yes, it runs on Odoo Enterprise.
How does change approval work?
Changes flagged as higher risk, and emergency changes, need CAB approval before implementation can start. Approvals are recorded with who, when and why.
Does the SLA clock pause?
Yes. Moving a ticket to On Hold pauses the SLA clock, and the pause history is auditable.
What happens when a problem is marked a known error?
If a workaround is documented, a knowledge-base article is created and linked to the problem.
Can we migrate existing tickets and assets?
Yes. Existing tickets and asset inventory can be imported during the build stage.
How long does it take and what does it cost?
It depends on ticket volume, CMDB complexity, integrations and configuration. We scope both after discovery.