Give every project and task a reference that never breaks
Automatic, immutable reference codes for projects, tasks, and sub-tasks — assigned correctly no matter how you create them, and visible everywhere from kanban cards to the customer portal.
Tasks and projects are identified only by internal database IDs or free-text names — meaningless the moment a customer, subcontractor, or another department needs to reference them. Popular numbering apps only work if you leave the project unset when creating a task, forcing an awkward two-step workaround, and none combine reliable sub-task numbering with portal visibility.
Every project and task gets a stable, human-readable code the instant it is created — correctly, whether or not a project is selected first. The code never changes, and flows automatically into kanban cards, list columns, forms, breadcrumbs, and the customer portal. A one-click retrofit codes every record you had before installing.
Everything a citable reference number needs
Every capability below is implemented in the module.
Correct on every creation path
Tasks are coded whether you set a project first, add it later, or leave it blank — the exact bug that trips up several competing apps.
Configurable prefix, suffix & separator
Set your own project and task prefixes, an optional suffix, separator character, and number padding from Settings — no code editing required.
Global or per-project task numbering
Choose a single running sequence for all tasks (TASK-0001) or a counter that resets per project (PRJ-0001-0001) — switch anytime from Settings.
Predictable sub-task numbering
Hierarchical numbering extends the parent's code (TASK-0001-01, TASK-0001-02), so nested work is readable at a glance — no more guessing at prefix logic.
Visible on every surface
The reference shows up in list columns, kanban card badges, form headers, and the search bar for both projects and tasks — consistently, with no extra setup.
Portal visibility for customers
Toggle reference codes on for portal users so clients and subcontractors can cite the exact task in emails, invoices, or support tickets — no separate configuration needed.
Quick-jump search by code
Type or paste a reference code into any Odoo search bar to open the matching record directly, or see a filtered list when several match.
Codes in names, breadcrumbs & chatter
Task display names are automatically prefixed with the code, so it carries through breadcrumbs, chatter, picker dropdowns, and any name-based printout.
One-click retrofit
A single button in Settings assigns reference codes to every project and task that existed before you installed the app, parents before children.
How it works
Configure once
Set prefixes, separator, padding, and numbering mode in Settings > Project.
Create as usual
Add a project or task the normal way. A code is assigned the moment it is saved, whichever order you fill in the fields.
Reference everywhere
The code shows on kanban cards, list columns, forms, breadcrumbs, and — if enabled — the customer portal.
Retrofit existing records
One click in Settings assigns codes to every project and task that predates installation.
See it in action
Reference codes shown consistently across every backend view and the customer portal.
Every project kanban card carries its reference badge, so the code is visible at a glance in the primary daily view.
A dedicated Reference column in the project list, searchable straight from the search bar.
The reference sits read-only near the project title on the form — visible, but never editable by accident.
Task cards show the reference badge too, including the hierarchical code on sub-tasks.
The task list carries the same Reference column, filterable and searchable by code.
On the task form, the code appears both as a dedicated field and prefixed into the breadcrumb title.
The Reference Numbering settings panel: prefixes, separator, padding, global vs. per-project numbering, hierarchical sub-tasks, portal visibility, and the retrofit button.
When portal visibility is enabled, customers see the reference code on their task list — no extra configuration needed.
The same code appears on the portal task detail page, giving customers a citation-safe reference for emails and support requests.
Frequently asked
Does the sequence still generate if I don't pick a project when creating a task?
Yes. That is the exact defect several competing apps have. A code is assigned the moment the task is saved, regardless of whether the project is set at creation or added afterward.
Can sub-tasks get their own numbering?
Yes. With hierarchical numbering on (the default), each sub-task's code extends its parent's code, for example TASK-0001-01, so the hierarchy is readable at a glance.
Will customers see these codes on the portal?
Yes, if portal visibility is enabled (on by default). Codes appear on the portal task list and task detail pages so clients can cite the correct reference in emails and support requests.
What happens to projects and tasks that already existed before I installed the app?
Use the "Assign missing references" button in Settings > Project > Reference Numbering. It codes every existing project and task in one click, coding parents before their sub-tasks.
Get in Touch
Have questions or need customization? Every purchase includes 30 days of free support — we are here to help.
Visit Our Website
www.cerevantix.comExplore our apps, services, and portfolio.
Empowering growth through technology.
Automatic, immutable reference codes for Odoo projects, tasks, and sub-tasks — visible on kanban, lists, forms, and the customer portal.
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Project (project)
• Discuss (mail) |
| Lines of code | 436 |
| Technical Name |
cerevantix_project_task_unique_sequence |
| License | OPL-1 |
| Website | https://cerevantix.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