| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Maintenance (maintenance) • Project (project) • Website (website) |
| Lines of code | 2403 |
| Technical Name |
tit_maintenance_portal_bridge |
| License | LGPL-3 |
| Website | https://www.trineevo.com |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Maintenance (maintenance) • Project (project) • Website (website) |
| Lines of code | 2403 |
| Technical Name |
tit_maintenance_portal_bridge |
| License | LGPL-3 |
| Website | https://www.trineevo.com |
Smart Maintenance Portal + Task Bridge
A complete portal, task bridge, SLA, assignment, proof, feedback, reopen, notification, and dashboard solution for Odoo Community Maintenance.
What this app solves
Requesters can report issues from the portal, technicians can execute work in Project, and managers can control SLA, assignment, overdue requests, feedback, and operational KPIs from one connected workflow.
Submit, track, message, rate, and reopen.
Work from linked Project tasks.
Monitor SLA, overdue work, and KPIs.
Trineevo Info Tech
Innovate - Automate - Elevate
Request intake
Project bridge
Deadline control
Manager dashboard
Configure
Settings, rules, stagesSubmit
Portal request and filesExecute
Linked Project taskReview
Feedback and dashboardWhy this module is useful
It connects public request submission with internal maintenance execution and management control.
Self-service requester portal
Portal users create requests, upload images/documents, track status, post messages, submit feedback, and reopen completed work when allowed.
Own request access Attachments FeedbackMaintenance to Project task bridge
Requests can automatically or manually create linked Project tasks, keeping technicians in their standard task workflow with maintenance details available.
Auto task Manual task Smart buttonsSLA, assignment, and duplicate control
SLA rules, assignment rules, duplicate detection, reminders, overdue flags, and escalation notifications reduce manual follow-up.
SLA deadline Assignment rules Duplicate checkManager dashboard and reporting
Managers monitor open, overdue, completed, reopened, unassigned, SLA breached, rating, stage, location, priority, and responsible-user data.
Clickable KPIs Filters Summary viewsRecommended setup sequence
Configure once, then let requesters, technicians, and managers work through the connected flow.
1. Enable settings
Open Settings and configure task creation, default project, SLA hours, assignment rules, duplicate checks, completion proof, reopen flow, and notifications.
2. Define operational rules
Create portal locations, SLA rules, assignment rules, and stage mappings according to your maintenance process.
3. Submit a request
Portal users open the maintenance page, enter issue details, choose equipment/location, add images or documents, and submit.
4. Execute the task
Technicians work from the linked Project task and keep maintenance request context visible from the task form.
5. Confirm or reopen
After completion, requesters can submit rating and feedback or reopen the request with a reason when reopen is enabled.
6. Monitor dashboard
Managers use dashboard filters and KPI cards to identify overdue, unassigned, reopened, completed, and SLA-breached requests.
Portal request management
Portal users can submit, track, communicate, provide feedback, and reopen requests from their account.
Maintenance and Project stay connected
Managers keep operational control in Maintenance while technicians execute work from Project tasks.
Dashboard for maintenance performance
Managers can filter and review operational performance without building custom reports.
Configurable for real maintenance operations
Administrators can enable only the flows they need and keep the app generic for any maintenance team.
Submission, tracking, messaging, feedback, and reopen.
Automatic and manual task creation with two-way smart buttons.
Maintenance and Project task stages can sync both ways.
Reminder, overdue, escalation, and manager summary scheduled jobs.
Route work by priority, category, equipment, location, and company.
Before/after proof, completion notes, feedback, rating, and reopen history.
Built for controlled Community deployments
The module avoids Enterprise-only dependencies, external APIs, and customer-specific logic.
Portal users can only access their own maintenance requests.
Email templates cover creation, assignment, stage change, SLA, overdue, completion, reopen, feedback, and daily summary flows.
Operational records and configuration respect company boundaries where applicable.
Innovate - Automate - Elevate
Need help before purchase?
Contact the author for product questions, implementation guidance, or customization discussion.
contact@trineevo.com
Trineevo Info Tech
Only standard Odoo Community apps are required: Maintenance, Project, Portal, Website, Mail, and Web.
Please log in to comment on this module