Technical Specifications & Compatibility
Technical Module Name
Supported Odoo Versions
v19.0
License
Odoo
Deployment Support
Odoo OnlineOdoo.shOn Premise
Lines of Code
1145 lines (Python / XML / JS)
Overview & Description
Odoo 19 Odoo 20 Community and Enterprise OPL-1 Version 19.0.1.0.0 Helpdesk with Working-Hours SLA Tickets, teams and SLA deadlines counted in working hours rather than wall-clock hours. The clock skips nights, weekends and public holidays, and stops entirely while you are waiting on the customer. A four-hour promise made at half past four on a Friday is due at half past eleven on Monday, not at half past eight on Saturday morning. Module Overview What this module solves. Odoo Community has no helpdesk The Helpdesk app is Enterprise, along with Planning, Approvals, Quality, Sign and Documents. What Community does have is the resource calendar, which already knows your working hours, your lunch break and your public holidays. This module is a helpdesk built on that. An SLA is not created plus four hours Adding a fixed offset promises the customer something you cannot deliver and then reports you as having missed it. Every deadline here is planned on the team's working calendar, so a bank holiday behaves exactly like a Sunday. And the clock stops. Move a ticket to a stage marked Clock Stops Here and the deadline pauses. When it resumes it moves out by the working hours waited, not the elapsed hours. A customer who takes the whole weekend to reply has cost the desk nothing, because the desk was shut. Key Features Everything included in the module. Working-Hours Clocks Deadlines planned on the team's working calendar Nights, weekends, lunch breaks and public holidays all skipped A four-hour promise at 16:30 Friday is due 11:30 Monday A ticket raised at ten at night starts at nine the next morning A desk with no calendar degrades to wall-clock rather than losing the deadline Clocks That Stop Any stage can be marked Clock Stops Here The deadline moves out by working hours waited, not elapsed hours Pausing twice does not double-count A ticket created straight into a paused stage starts paused Closing from a paused stage counts the wait before scoring SLA Policies First Reply and Resolution targets, in working hours Conditions on priority, tags and customers An empty condition means everything, so a blank policy is the blanket promise Policies stack: a ticket collects every one that matches A policy from another team never applies Honest Escalation Raising the priority attaches the stricter promise Counted from when the clock started, not from the escalation A three-hour-old ticket breaches a one-hour promise immediately Lowering the priority drops a running clock but never a finished one Moving teams swaps one desk's promises for the other's Tickets Reference, subject, customer, team, assignee, priority and tags Kanban by stage, list, and a form with the full clock table Ordered by priority then soonest deadline Filters for My, Unassigned, Open, SLA Missed, Due Today and Urgent Chatter, activities and followers on every ticket Teams Each team has its own working calendar, board and policies Email alias: mail to the team address becomes a ticket Assignment by hand, or to the agent carrying the fewest open tickets Closed tickets do not count against anybody Open and breached counts shown on the team list Business Benefits Why it matters day to day. Promises You Can Keep Deadlines fall inside hours somebody is actually working, so the target you quoted is the target you can hit. Fair Breach Reporting Waiting on the customer does not count against the desk, and a weekend of silence does not hand agents free slack either. One Desk, Many Regions A team in Europe and a team in Asia turn the same four-hour number into different real deadlines, from their own calendars. A True Morning List An hourly job marks clocks that have run out, so what is late is late before anybody opens a ticket. Screenshots A tour of the interface. Ticket Kanban Screenshot Placeholder Stages across the board, with priority and SLA state on each card. Ticket Form And Clock Table Screenshot Placeholder Every policy on the ticket, its deadline and whether it was met. SLA Policy Setup Screenshot Placeholder Target hours, type, and the conditions that decide who it applies to. Team And Working Hours Screenshot Placeholder The calendar, the email alias and the assignment method. Workflow From a raised ticket to a kept promise. Set the team's working hours. Point the Support team at a calendar that matches reality, including its public holidays. Every deadline is planned on it. Write the promises. A blanket reply target, a stricter one for urgent tickets, a resolution target. Leave a condition empty and it means everything. A ticket arrives. Raised by hand or by email to the team alias. It collects every policy that matches, and each gets its own clock. An agent replies. A reply to the customer stops the first-reply clock. Internal notes and tracking messages do not, and only the first reply counts. Waiting on the customer. Move it to the paused stage and the clock stops. Moving it back pushes the deadline out by the working hours waited. Close it. A closing stage stops the resolution clock and scores the result. Reopening is recorded as a reopen, not as a fresh promise. What Stops Which Clock Event First Reply clock Resolution clock Agent replies to the customer Stopped and scored Still running Agent posts an internal note Still running Still running Customer sends an email Still running Still running Moved to Waiting on Customer Paused Paused Moved to a closing stage Scored as it stood Stopped and scored Reopened after closing Not resurrected Recorded as a reopen Configuration Menus, stages, roles and the hourly job. Menu Structure Menu Purpose Tickets, then My Tickets What this agent is carrying Tickets, then All Tickets The whole board, in kanban, list and form Tickets, then Breached Everything that has missed a promise Configuration, then Teams Calendars, aliases and assignment Configuration, then Stages The board columns and their two flags Configuration, then SLA Policies and Tags The promises themselves, and ticket tags Stage Flags Flag Effect Closing Stage Resolves the ticket and stops the resolution clock Clock Stops Here Suspends every running clock while the ticket sits there Neither An ordinary working column; clocks keep running A stage cannot be both. Closing and pausing are opposite claims about whose turn it is, so the two flags are mutually exclusive. Installed Ready To Use Item What ships Team Support Stages New, In Progress, Waiting on Customer, Solved, Cancelled Reply policy Reply the same working day 4 h Urgent reply policy Urgent tickets answered within the hour 1 h Resolution policy Fixed within three working days 24 h Scheduled job Helpdesk: mark missed SLAs, hourly Set the team's Working Hours before you rely on a deadline. Everything is planned on that calendar, so a team pointed at the wrong one makes the wrong promises. A paused clock is never marked late by the hourly job. Technical Details Models, dependencies and design. Module Information Technical Name helpdesk_sla_aura Version 19.0.1.0.0 Category Services / Helpdesk License OPL-1 Dependencies base, mail, resource. No accounting, no website. External Libraries None beyond a standard Odoo installation External Service None. Everything runs inside your own Odoo instance. Automated Tests 59 tests, including a browser tour Models Model Description helpdesk.team A desk, its calendar, its alias and its board helpdesk.ticket The ticket, with chatter and activities helpdesk.stage A board column with its closing and pausing flags helpdesk.sla A promise: type, target hours and conditions helpdesk.ticket.sla.status One clock on one ticket, with its deadline and result helpdesk.tag Ticket tags, usable as a policy condition Design Notes Built on the resource calendar. Deadlines are planned with leaves taken into account, which is what makes a bank holiday behave like a Sunday. Pausing pushes by working hours. Pushing by elapsed time would hand an agent sixty-five hours of free slack for a wait that cost two. An explicit start field. The creation date cannot be written in Odoo, so a backlog imported from another system carries its real raise time here instead. A reply is not a fix. First reply and resolution are separate clocks scored separately, and the module does not pretend one implies the other. Escalation cannot be gamed. A stricter promise is counted from when the clock started, not from the moment of escalation. Starting it at escalation would let anybody dodge a breach by re-tagging a ticket that had already been sitting for hours. Compatibility Where the module runs. Item Supported Odoo Version 19.0 Current Hosting Odoo.sh, On-Premise and any self-managed deployment Multi-Company Yes, with record rules on teams, tickets and policies Multi-Timezone Yes, each team plans on its own working calendar Multi-Language Yes, stages, policies and messages are translatable Incoming Email Yes, each team can have its own alias Mobile and Tablet Yes, standard responsive Odoo web client Supported Editions Both editions, one code base. Community Edition Supported The edition this module was written for. It brings a helpdesk with real SLA clocks to an Odoo that has neither. Enterprise Edition Supported Runs on Enterprise with its own models and menus, so it does not collide with the standard Helpdesk app. Odoo.sh Supported No extra Python packages to install, so it deploys with no change to your build configuration. Installation Four steps to a running desk. Copy the module. Place the helpdesk_sla_aura folder in your Odoo addons path, then update the apps list from developer mode. Install Helpdesk with Working-Hours SLA. Only base, mail and resource are required. Set the team's Working Hours. Open the Support team and point it at a calendar that matches reality, including its public holidays. Assign the roles. Give support staff Agent and supervisors Helpdesk Manager, then adjust the three installed policies to your own targets. A Support team, five stages and three sensible policies are installed with the module, so the desk is usable the moment the working calendar is set. Frequently Asked Questions The questions asked most often. A normal deadline adds a fixed offset, so a four-hour promise made at 16:30 on a Friday falls at 20:30 that evening or, counted as elapsed time, in the middle of Saturday. Here the four hours are spent only on the team's working calendar, so it lands at 11:30 on Monday: a time somebody is actually there to meet it. Yes. Deadlines are planned with the calendar's leaves taken into account, so a bank holiday on the team's calendar behaves exactly like a Sunday. Lunch breaks are skipped for the same reason. The clock stops. When the ticket comes back the deadline moves out by the working hours it spent waiting, not the elapsed hours. A customer who takes the whole weekend costs the desk nothing, and equally nobody gains sixty-five hours of slack from a wait that really cost two. Yes, policies stack. A blanket four-hour reply, a one-hour reply for urgent tickets and a two-hour reply for a key account can all sit on the same ticket, each with its own clock. A policy with nothing filled in is the team's blanket promise, and a policy belonging to another team never applies. Something an agent actually said to the customer. Internal notes, tracking messages and the customer's own emails do not stop the clock, and only the first reply counts. Closing the ticket is what stops the resolution clock, because a reply is not a fix. Because raising the priority is an admission that it was urgent all along. The stricter promise is counted from when the clock started, so a ticket that has been sitting for three hours breaches a one-hour promise the moment somebody says so. Counting from the escalation instead would let anybody dodge a breach by re-tagging. Yes. Each team can have its own email alias, and mail sent to it becomes a ticket on that team's board with the sender as the customer. Tickets can also be assigned automatically to whichever agent is carrying the fewest open ones. Neither, deliberately. Nobody logs in to see their own tickets, and the list, the kanban and the group-bys are the reporting there is. Escalation actions are also left out: a breach is recorded and surfaced, and who gets told is a job for Odoo's automated actions watching the SLA state. Changelog Release history. Version 19.0.1.0.0 Initial Release SLA deadlines planned on the team's working calendar Nights, weekends, lunch breaks and public holidays skipped Clock Stops Here stages that pause every running clock Resuming pushes the deadline by working hours waited, not elapsed First Reply and Resolution policies with stacking conditions Escalation counted from the clock start, so it cannot be gamed Agent replies distinguished from notes and tracking messages Teams with their own calendar, board, policies and email alias Round-robin assignment to the least-loaded agent Kanban, list and form with a per-ticket clock table Filters for My, Unassigned, SLA Missed, Due Today and Urgent Agent and Helpdesk Manager roles with multi-company rules Hourly job marking missed SLAs, never a paused one A Support team, five stages and three policies installed ready to use 59 tests, including a browser tour Support We answer, and we keep our modules current. Email odooaura@gmail.com Website www.auraodoo.tech YouTube youtube.com/@Auraodoo Free support for bug fixes on the Odoo version you downloaded. Customisation and installation help available on request. Aura Odoo Tech Odoo modules built to be understood, not just installed. Odoo 19 OPL-1 helpdesk_sla_aura www.auraodoo.tech | odooaura@gmail.com | youtube.com/@Auraodoo
Key Capabilities & Features
- Deadlines planned on the team's working calendar
- Nights, weekends, lunch breaks and public holidays all skipped
- A four-hour promise at 16:30 Friday is due 11:30 Monday
- A ticket raised at ten at night starts at nine the next morning
- A desk with no calendar degrades to wall-clock rather than losing the deadline
- Any stage can be marked Clock Stops Here
- The deadline moves out by working hours waited, not elapsed hours
- Pausing twice does not double-count
- A ticket created straight into a paused stage starts paused
- Closing from a paused stage counts the wait before scoring
- First Reply and Resolution targets, in working hours
- Conditions on priority, tags and customers
- An empty condition means everything, so a blank policy is the blanket promise
- Policies stack: a ticket collects every one that matches
- A policy from another team never applies
- Raising the priority attaches the stricter promise
- Counted from when the clock started, not from the escalation
- A three-hour-old ticket breaches a one-hour promise immediately
- Lowering the priority drops a running clock but never a finished one
- Moving teams swaps one desk's promises for the other's
- Reference, subject, customer, team, assignee, priority and tags
- Kanban by stage, list, and a form with the full clock table
- Ordered by priority then soonest deadline
- Filters for My, Unassigned, Open, SLA Missed, Due Today and Urgent
- Chatter, activities and followers on every ticket
- Each team has its own working calendar, board and policies
- Email alias: mail to the team address becomes a ticket
- Assignment by hand, or to the agent carrying the fewest open tickets
- Closed tickets do not count against anybody
- Open and breached counts shown on the team list
- Set the team's working hours. Point the Support team at a calendar that matches reality, including its public holidays. Every deadline is planned on it.
- Write the promises. A blanket reply target, a stricter one for urgent tickets, a resolution target. Leave a condition empty and it means everything.
- A ticket arrives. Raised by hand or by email to the team alias. It collects every policy that matches, and each gets its own clock.
- An agent replies. A reply to the customer stops the first-reply clock. Internal notes and tracking messages do not, and only the first reply counts.
- Waiting on the customer. Move it to the paused stage and the clock stops. Moving it back pushes the deadline out by the working hours waited.
- Close it. A closing stage stops the resolution clock and scores the result. Reopening is recorded as a reopen, not as a fresh promise.
- Built on the resource calendar. Deadlines are planned with leaves taken into account, which is what makes a bank holiday behave like a Sunday.
- Pausing pushes by working hours. Pushing by elapsed time would hand an agent sixty-five hours of free slack for a wait that cost two.
- An explicit start field. The creation date cannot be written in Odoo, so a backlog imported from another system carries its real raise time here instead.
- A reply is not a fix. First reply and resolution are separate clocks scored separately, and the module does not pretend one implies the other.
- Copy the module. Place the helpdesk_sla_aura folder in your Odoo addons path, then update the apps list from developer mode.
- Install Helpdesk with Working-Hours SLA. Only base, mail and resource are required.
- Set the team's Working Hours. Open the Support team and point it at a calendar that matches reality, including its public holidays.
- Assign the roles. Give support staff Agent and supervisors Helpdesk Manager, then adjust the three installed policies to your own targets.
- SLA deadlines planned on the team's working calendar
- Nights, weekends, lunch breaks and public holidays skipped
- Clock Stops Here stages that pause every running clock
- Resuming pushes the deadline by working hours waited, not elapsed
- First Reply and Resolution policies with stacking conditions
- Escalation counted from the clock start, so it cannot be gamed
- Agent replies distinguished from notes and tracking messages
- Teams with their own calendar, board, policies and email alias
- Round-robin assignment to the least-loaded agent
- Kanban, list and form with a per-ticket clock table
- Filters for My, Unassigned, SLA Missed, Due Today and Urgent
- Agent and Helpdesk Manager roles with multi-company rules
- Hourly job marking missed SLAs, never a paused one
- A Support team, five stages and three policies installed ready to use
- 59 tests, including a browser tour
- The author can leave a single reply to each comment.
- This section is meant to ask simple questions or leave a rating. Every report of a problem experienced while using the module should be addressed to the author directly (refer to the following point).
- If you want to start a discussion with the author or have a question related to your purchase, please use the support page.
Screenshots & Previews
1 image availableExpand Preview
The AuraOdoo Quality Guarantee
100% Tested
Verified with Odoo 17, 18, and 19 test pipelines for stability and no conflicts.
Clean Architecture
Built according to official Odoo guidelines and PEP 8 standards with zero bloat.
Dedicated Support
Free installation assistance and quick bug turnaround from our team.