Project Suite All-in-One for Odoo | Agile Scrum, Service Desk & SLA, Flow Analytics, Stage Guards | Project Bundle
by CODEerts https://www.codeerts.com$ย 299.00
In-App PurchasesProject Suite All-in-One for Project
Agile Scrum, a Service Desk with SLA, flow analytics, stage guards and GitHub branches.
Five CODEerts Project apps in one install, inside the standard Project app.
Everything your delivery, support and management teams need on top of the standard Project app. No Enterprise edition required.
|
5-in-1
One Install
|
SLA
On Working Hours
|
Burndown
& Flow Analytics
|
Guards
Stage Gates
|
Odoo 19
Compatible
|
The project stack every growing team ends up needing
Odoo Project handles tasks, but real teams need agile, support and analytics too
|
Five needs, five installs
Scrum, a service desk, reporting, workflow gates and a link to your Git repository usually mean five separate apps to buy, install and keep in sync. |
No SLA or customer portal
Standard Project has no working-hours SLA timers and no self-service portal for clients to raise and track requests. |
No flow metrics or gates
There is no cycle time, burndown or cumulative flow, and nothing stops a task jumping a stage before it is truly done. |
What this module does
Project Suite bundles the whole CODEerts Project range into one module, living inside the standard Project app rather than a second app tile. It brings Scrum and Kanban to Odoo Project with sprints, a backlog, story points, a sprint board, WIP-limit badges, epics with automatic point rollup and a velocity chart.
It turns Project into a service desk with SLA policies measured on working hours, breach escalation, request types and a customer portal. It adds flow analytics such as cycle time, cumulative flow and sprint burndown on native graph and pivot views. And it enforces stage-transition guards that block a task from a stage until required fields are set, sub-tasks are done or a custom rule passes. It puts a Create Branch button on the task form, so a developer creates a GitHub branch from the task itself and the branch is recorded on the task with a link, while the access token stays readable only by a Git Administrator. Everything is multi-company and builds on the standard Project app.
|
๐
Agile Scrum
Sprints, backlog, story points, a sprint board with WIP-limit badges, epics with automatic rollup and a velocity chart. |
๐ง
Service Desk & SLA
SLA policies on working hours, breach escalation, request types and a public and logged-in customer portal. |
๐
Flow Analytics
Cycle time, lead time and cumulative flow on graph and pivot, plus daily sprint burndown snapshots. |
๐ก
Stage Guards
Block a task from a stage until required fields, all sub-tasks done or a custom rule pass, with a clear message. |
๐ฟ
GitHub Branches
Create a GitHub branch from a task and see it on the task with a link. Only a Git Administrator can read the access token. |
|
๐ฏ Sprints & Story Points
Time-box work into sprints, estimate a backlog in points, and return unfinished tasks to the backlog on close. |
๐ฆ WIP Limits & Epics
A live badge warns when a kanban column is overloaded, and epics roll up their points and progress automatically. |
|
โฑ Working-Hours SLA
Response and resolution targets per priority and request type, paused outside your business hours, with breach escalation. |
๐ค Customer Portal
A public intake form at /servicedesk and a logged-in area where clients raise and follow their own tickets. |
|
๐ Cycle Time & Burndown
Cycle time per stage, cumulative flow and daily sprint burndown, on the native graph and pivot views you know. |
๐ก Definition of Done Gates
Stage guards enforce required fields, completed sub-tasks or a custom domain before a task can move on. |
|
๐ข Multi-Company
Sprints, SLA policies, analytics and guards each carry a company and are filtered by multi-company record rules. |
๐งฉ Builds on Standard Project
Adds to the Odoo Project app you already use and runs on Community as well as Enterprise. No core data changed. |
|
๐ฟ Branch from a Task
A Create Branch button on the task form, with the repository list limited to the repositories that task's project is allowed to use and the name suggested from the task. |
๐ Token Stays With the Admin
A Git User creates branches; only a Git Administrator can read the stored access token, so a whole delivery team gets the feature without holding a write-scope credential. |
How it works
1 |
Install once, get one Project Suite menu A single install adds a unified Project Suite menu with Agile, Service Desk, Reporting and Configuration sections. |
2 |
Run Scrum on the sprint board Estimate the backlog in story points, pull tasks into a sprint, and run a board with WIP-limit badges on every column. |
3 |
Open the service desk and portal Define SLA policies on working hours, enable the portal on a project, and let customers raise and track tickets. |
4 |
Read flow analytics and burndown Watch cycle time, cumulative flow and a daily sprint burndown to spot bottlenecks and keep sprints on track. |
5 |
Gate your stages with guards Define a Definition of Done per stage so a task cannot advance until its fields, sub-tasks or custom rule pass. |
Screenshot walkthrough
One suite, from an agile board to a stage guard.
Run your sprint board grouped by stage, with a live badge on every column that turns red the instant it goes over its WIP limit.
Committed versus delivered points across completed sprints, so you forecast the next commitment from your real throughput.
Define response and resolution targets per priority and request type, measured on business hours and escalated on breach.
Clients raise and track their own requests in a self-service portal, each with a live SLA status badge and due date.
See how long work spends in each stage on native graph and pivot views, and find the step where delivery slows down.
A daily snapshot of remaining story points, so you can tell at a glance whether the current sprint is on track.
Define gates that block a task from a stage until required fields are set, sub-tasks are done, or a custom rule passes.
Agile, Service Desk, Reporting and Configuration are sections of Project, not a second app. Our reports sit beside Odoo's own, so your team finds them where they already look.
The Development tab lists every branch created for the task with a link that opens it on GitHub. Press Create Branch and the next one is made without leaving Odoo, and without the developer ever seeing the access token.
Technical information
|
Version
19.0
|
License
OPL-1
|
Editions
Community & Enterprise
|
Dependencies
project, website, resource, base_automation (core)
|
Technical name: codeerts_project_suite ยท Includes: Agile Scrum, Service Desk & SLA, Flow Analytics, Stage Guards
What's New
Upgrades are free for the lifetime of your purchase.
- Create a GitHub branch straight from a task, and see it on the task with a link.
- The access token is readable only by a Git Administrator, so developers create branches without ever holding the credential.
- Agile, Service Desk, Reporting and Configuration now live inside the standard Project app. There is no second app tile to learn.
- Menu sequences align with the individual Project apps, so installing the suite alongside them interleaves cleanly instead of duplicating sections.
Frequently asked questions
Five capabilities in one module: Agile Scrum (sprints, backlog, story points, sprint board, WIP limits, epics, velocity), a Service Desk with working-hours SLA timers and a customer portal, flow analytics with sprint burndown, stage-transition guards, and a GitHub integration that creates a branch straight from a task while keeping the access token with the administrator. They install together inside the standard Project app, so your team finds everything under Project rather than in a separate menu.
No. Project Suite is a single purchase and a single install that carries all five capabilities, priced below the total of the individual apps. If you only need one area, the standalone apps are still available.
It extends it. Project Suite builds on the standard Project app, so your existing projects, tasks and stages keep working and simply gain sprints, SLA fields, analytics and stage guards on top.
No. The suite builds on the standard Project app and runs on Community as well as Enterprise. It depends only on core modules: Project, Website, Resource and Base Automation.
Yes. Sprints, SLA policies, analytics records and stage guards each carry a company and are filtered by multi-company record rules, so each company sees only its own configuration.
Use the version selector at the top of this page to pick your Odoo release. Project Suite 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 |
100+ 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 | 2037 |
| Technical Name |
codeerts_project_suite |
| 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