sales_team_operating_unit
in operating-unit · source on GitHub
Category: Sales · ForgeFlow · SerpentCS · LGPL-3
| Series | Status | Details | Code |
|---|---|---|---|
| 16.0 | ✓Installs | · run 2026-08-21 · 16.0.1.0.0 | on GitHub |
| 17.0 | ✓Installs | · run 2026-08-21 · 17.0.1.0.0 | on GitHub |
| 18.0 | ✓Installs | · run 2026-09-15 · 18.0.1.0.1 | on GitHub |
| 19.0 | ✓Installs | · run 2026-08-19 · 19.0.1.0.0 | on GitHub |
| 20.0 | —Not tested | no branch |
Odoo 20.0 dev — development line
A different statement from the table above. There: the module as published, on a released platform. Here: the module’s code with its manifest version mechanically raised, on a platform that has not been released and changes daily.
| Status | Details |
|---|---|
| ✗fails | The same code installs on 19.0; on the development line it does not. The difference belongs to the platform. (access_model) · version 19.0.1.0.0 → 19.5.1.0.0, code unchanged · run 2026-09-11 · odoo 19.5 · modidx/odoo:master-deps-20260910 |
Log excerpt, 20.0 dev
2026-09-11 00:22:24,105 1 INFO job_88afe68dd66d odoo.addons.base.models.ir_module: ALLOW access to module.button_install on ['Sales Team Operating Unit'] to user __system__ #1 via n/a
2026-09-11 00:22:24,941 1 INFO job_88afe68dd66d odoo.modules.loading: loading 32 modules...
2026-09-11 00:22:25,124 1 INFO job_88afe68dd66d odoo.modules.loading: Loading module operating_unit (15/32)
2026-09-11 00:22:25,140 1 WARNING job_88afe68dd66d odoo.modules.loading: Transient module states were reset
2026-09-11 00:22:25,141 1 ERROR job_88afe68dd66d odoo.registry: Failed to load registry
2026-09-11 00:22:25,142 1 CRITICAL job_88afe68dd66d odoo.service.server: Failed to initialize database `job_88afe68dd66d`.
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/odoo/service/server.py", line 1559, in preload_registries
registry = Registry.new(dbname, update_module=update_module, install_modules=config['init'], upgrade_modules=config['update'], reinit_modules=config['reinit'])
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3/dist-packages/odoo/tools/func.py", line 67, in locked
return func(inst, *args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3/dist-packages/odoo/orm/registry.py", line 222, in new
contextvars.Context().run(
File "/usr/lib/python3/dist-packages/odoo/modules/loading.py", line 446, in load_modules
load_module_graph(
File "/usr/lib/python3/dist-packages/odoo/modules/loading.py", line 181, in load_module_graph
model_names = registry.load(package)
^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3/dist-packages/odoo/orm/registry.py", line 442, in load
model_cls = model_classes.add_to_registry(self, model_def)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3/dist-packages/odoo/orm/model_classes.py", line 188, in add_to_registry
raise TypeError(f"Model {name!r} does not exist in registry.")
TypeError: Model 'ir.rule' does not exist in registry.
2026-09-11 00:22:25,147 1 INFO job_88afe68dd66d odoo.service.server.ThreadedServer: Initiating shutdown
2026-09-11 00:22:25,147 1 INFO job_88afe68dd66d odoo.service.server.ThreadedServer: Hit CTRL-C again or send a second signal to force the shutdown.
2026-09-11 00:22:25,148 1 INFO job_88afe68dd66d odoo.addons.bus.websocket: Disconnecting 0 websockets
2026-09-11 00:22:25,249 1 INFO job_88afe68dd66d odoo.sql_db: ConnectionPool(read/write;used=0/count=0/max=64): Closed 1 connectionsProvenance: __manifest__.py sha256 9570057c707eda3b… · tree of 18 files without the manifest, sha256 30977b99b884ea04…
This does not say the module is compatible with Odoo 20.0, and does not say it installs on Odoo 20.0 — on a stock platform it will not, until its maintainer raises the version. Why we raise the version
Odoo 20.0 — the branch itself
The same frozen code, run again against the real 20.0 branch. The run above used Odoo’s development line before the branch was cut; this one used the branch, pinned to one commit.
| Status | Details |
|---|---|
| ✗fails | The same code installs on 19.0; on the development line it does not. The difference belongs to the platform. (access_model) · version 19.0.1.0.0 → 20.0.1.0.0, code unchanged · run 2026-09-18 · odoo 20.0 · modidx/odoo:20.0-deps-20260918 |
Log excerpt, 20.0 dev
2026-09-18 22:08:18,818 1 INFO job_c098347e63a7 odoo.modules.loading: loading 31 modules...
2026-09-18 22:08:19,781 1 WARNING job_c098347e63a7 odoo.addons.mail.controllers.attachment: markdown2 is not installed, markdown will not be rendered
2026-09-18 22:08:19,857 1 INFO job_c098347e63a7 odoo.modules.loading: Loading module operating_unit (17/31)
2026-09-18 22:08:19,869 1 WARNING job_c098347e63a7 odoo.modules.loading: Transient module states were reset
2026-09-18 22:08:19,870 1 ERROR job_c098347e63a7 odoo.registry: Failed to load registry
2026-09-18 22:08:19,870 1 CRITICAL job_c098347e63a7 odoo.service.server: Failed to initialize database `job_c098347e63a7`.
Traceback (most recent call last):
File "/opt/odoo/odoo/service/server.py", line 1520, in preload_registries
registry = Registry.new(dbname, update_module=update_module, install_modules=config['init'], upgrade_modules=config['update'], reinit_modules=config['reinit'])
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/opt/odoo/odoo/tools/func.py", line 67, in locked
return func(inst, *args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/opt/odoo/odoo/orm/registry.py", line 222, in new
contextvars.Context().run(
File "/opt/odoo/odoo/modules/loading.py", line 449, in load_modules
load_module_graph(
File "/opt/odoo/odoo/modules/loading.py", line 181, in load_module_graph
model_names = registry.load(package)
^^^^^^^^^^^^^^^^^^^^^^
File "/opt/odoo/odoo/orm/registry.py", line 442, in load
model_cls = model_classes.add_to_registry(self, model_def)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/opt/odoo/odoo/orm/model_classes.py", line 188, in add_to_registry
raise TypeError(f"Model {name!r} does not exist in registry.")
TypeError: Model 'ir.rule' does not exist in registry.
2026-09-18 22:08:19,873 1 INFO job_c098347e63a7 odoo.service.server.ThreadedServer: Initiating shutdown
2026-09-18 22:08:19,873 1 INFO job_c098347e63a7 odoo.service.server.ThreadedServer: Hit CTRL-C again or send a second signal to force the shutdown.
2026-09-18 22:08:19,873 1 INFO job_c098347e63a7 odoo.addons.bus.websocket: Disconnecting 0 websockets
2026-09-18 22:08:19,974 1 INFO job_c098347e63a7 odoo.sql_db: ConnectionPool(read/write;used=0/count=0/max=64): Closed 1 connectionsProvenance: __manifest__.py sha256 9570057c707eda3b… · tree of 18 files without the manifest, sha256 30977b99b884ea04…
This does not say the module is compatible with Odoo 20.0, and does not say it installs on Odoo 20.0 — on a stock platform it will not, until its maintainer raises the version. Why we raise the version
The module’s code on 19.0
| Lines of code | python 111 · xml 75 |
| Tests | yes: 1 file(s), 72 lines |
| Migration scripts | no |
| Models | 0 new · 1 extensions |
Lines are physical, blanks and comments included, as wc -l. Tests are test_*.py files under tests/. Models are lines holding _name = and _inherit =. These are facts about the code, not a judgement: more lines is neither better nor worse. Measured 2026-08-28 on tree 0ccb488e9452.
The apps.odoo.com catalogue has a listing under the same technical name on 16.0: apps.odoo.com/apps/modules/16.0/sales_team_operating_unit. A matching name does not prove matching code — how we counted this.
Depends on
| Module | Status | Checked |
|---|---|---|
| operating_unit | ✓Installs | 2026-08-19 |
| sales_team | core | ships with Odoo |
Depended on by
2 modules on 19.0 declare this one as a dependency.
History
| Last change | 2025-11-24 |
| Code commits, 12 months | 20 |
| Most active | Jesús Alan Ramos Rodríguez, Bhavesh Heliconia, Jérémy Didderen |
| Files | 19 |
Translation and bot commits are excluded from the commit count.
Result looks wrong? Tell us — we will show the log or run it again. Report a wrong result