Service Desk & SLA for Project | Odoo Help Desk Ticketing | SLA Timers & Portal | Jira Service Management Alternative
by CODEerts https://www.codeerts.com$ย 129.00
Service Desk & SLA for Project
Turn Odoo Project into a help desk.
SLA timers on working hours, a public intake form and a customer ticket portal.
Response and resolution deadlines, breach tracking and a portal where customers follow their own tickets. No Enterprise edition required.
|
SLA
Policies
|
2
Deadlines Tracked
|
Portal
Customer Facing
|
Hourly
Breach Check
|
Odoo 18
Compatible
|
The support gap every Odoo team knows
Odoo Project holds tasks, but it does not run like a service desk
|
No SLA clock
There is no response or resolution deadline, so nobody knows when a ticket is late until a customer complains. |
Timers ignore working hours
A plain deadline counts overnight and weekends, so a four-hour SLA quietly breaches while the office is closed. |
Customers are left in the dark
There is no self-service portal, so clients cannot raise a request or see the status of one they already sent. |
What this module does
Service Desk & SLA turns the standard Odoo Project app into a help desk. Define SLA policies that set a response and a resolution deadline based on your working calendar, so the timers pause outside business hours instead of running through the night.
Every ticket shows its SLA policy, its deadlines and a live status of in progress, met or breached, and an hourly job flags breaches for you. A public form lets anyone raise a request, and a customer portal lets logged-in clients track their own tickets and follow the conversation.
|
โฑ
SLA on Working Hours
Response and resolution deadlines calculated on your business calendar, so timers pause overnight and at weekends and stay realistic. |
๐จ
Live Status & Breach Alerts
Each ticket shows in progress, met or breached at a glance, and an hourly scheduled job re-checks open tickets so a breach never goes unseen. |
๐ค
Customer Portal
A public form to raise a request and a My Service Desk portal where customers track their tickets, see the SLA badge and follow up in a message thread. |
|
๐ SLA Policies
Define a response time and a resolution time, matched to a priority, request type and working calendar. |
๐ท Request Types
Tag every ticket as a question, incident, change or problem and route it to the right SLA policy. |
|
๐ฅ Public Intake Form
A form at /servicedesk where anyone can raise a request that becomes an SLA-tracked ticket. |
๐ Customer Ticket Portal
Logged-in customers track their tickets with status, SLA badge and due date at /my/servicedesk. |
|
๐ฌ Conversation Thread
The portal ticket page has a message thread so customers can follow up and your team can reply. |
โฐ Hourly Breach Check
A scheduled job re-evaluates open tickets every hour so a breach is flagged the moment the deadline passes. |
|
๐ข Multi-Company Ready
SLA policies are scoped per company or shared across all, and record rules keep each company to its own tickets. |
๐งฉ Builds on Standard Project
Adds to the Project app you already use and runs on Community as well as Enterprise. No core data changed. |
How it works
1 |
Define your SLA policies Set a response and a resolution time, choose the priority and request type they apply to, and pick a working calendar. |
2 |
Enable the portal on a project Tick the service-desk portal option on the projects you want to accept and expose customer tickets for. |
3 |
Tickets arrive and match an SLA A request from the public form becomes a ticket, matches the right policy, and gets response and resolution deadlines. |
4 |
Work the ticket, watch the clock The ticket shows its live SLA status. The hourly job flags a breach the moment a deadline passes. |
5 |
Customers self-serve Clients track their tickets and SLA status from the portal and follow up in the message thread, without emailing you. |
Screenshot walkthrough
Follow one customer request from the inbox to a met SLA.
All incoming requests grouped by stage, with priority, type and assignee, so your team always knows what to pick up next.
Each ticket carries a request type, a priority and its live SLA countdown on top of the standard Odoo task, so agents work one familiar screen.
Define as many policies as you need, each matching a priority and a request type, with its own response and resolution targets.
Set the response and resolution hours and the working-hours calendar. Deadlines are then computed in business time, not wall-clock time.
A dedicated view of every request that has blown its resolution deadline, so nothing quietly slips past its SLA.
Signed-in customers see their own requests with a live SLA badge, On Track, In Progress or Breached, and the resolution due date on every row.
Customers open a request to read its full history and reply, keeping every message on the ticket instead of scattered across email.
Technical information
|
Version
18.0
|
License
OPL-1
|
Editions
Community & Enterprise
|
Dependencies
project, website
|
Technical name: codeerts_project_servicedesk ยท Adds: SLA policies, request types, breach cron, public form, customer portal, multi-company rules
Frequently asked questions
The module adds an SLA Policy model. Set a response and a resolution time, pick the priority and request type it applies to and a working calendar. Each matching ticket then shows its deadlines and a live SLA status.
Yes. Each policy points to a working calendar, so the response and resolution deadlines are calculated on business hours and pause overnight and at weekends, giving realistic due times.
Yes. A public form at /servicedesk lets anyone raise a request, and logged-in customers get a portal at /my/servicedesk that lists their tickets with status, SLA badge and due date, plus a detail page with a message thread to follow up.
Yes. SLA policies can be scoped to one company or left shared across all, and record rules keep each company to its own policies and tickets, so a multi-company database stays cleanly separated.
Use the version selector at the top of this page to pick your Odoo release. The module builds on the standard Project app and works on both Community and Enterprise.
The team behind this module
About CODEerts
Full-Service Odoo ERP Agency ยท Solutions That Scale
Every module in our store is built from real client work, tested in production and maintained long-term by a team of Odoo certified consultants. When you need more than an app, we deliver the full solution.
|
๐๏ธ Implementation
Full Odoo roll-outs from requirements to go-live, across any industry and company size. |
๐งฉ Custom Development
Bespoke modules, OWL components and business logic built precisely to your workflow. |
๐ Migrations
Zero-data-loss upgrades from older Odoo versions with full custom module porting. |
|
๐ Integrations
Payment gateways, shipping carriers, biometric devices, eCommerce and third-party APIs. |
๐ Odoo Audits
Performance, security and code-quality reviews that surface risks before they become problems. |
๐งโ๐ป Support & Training
Ongoing helpdesk, user training and monthly retainers so your team stays productive. |
Odoo Certified |
6+ Years |
50+ Projects |
10+ Industries |
40+ Published Apps |
More from CODEerts
Other apps we build to make Odoo do more. Tap any card to open it on the Odoo Apps Store.
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Project (project)
• Website (website) • Discuss (mail) |
| Lines of code | 576 |
| Technical Name |
codeerts_project_servicedesk |
| License | OPL-1 |
| Website | https://www.codeerts.com |
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module