project_hr_expense_analytic
in project · source on GitHub
Link expenses to a project and a task
Category: Accounting · Camptocamp · AGPL-3
| Series | Status | Details | Code |
|---|---|---|---|
| 16.0 | —Not tested | no branch | |
| 17.0 | —Not tested | no branch | |
| 18.0 | —Not tested | no branch | |
| 19.0 | ✓Installs | · run 2026-08-27 · 19.0.1.0.0 | on GitHub |
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 |
|---|---|
| ✓runs | · version 19.0.1.0.0 → 19.5.1.0.0, code unchanged · run 2026-09-10 · odoo 19.5 · modidx/odoo:master-deps-20260910 |
Provenance: __manifest__.py sha256 5ee4b384bf8192cf… · tree of 17 files without the manifest, sha256 b7d7c883455deeb7…
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 130 · xml 14 |
| Tests | yes: 1 file(s), 58 lines |
| Migration scripts | no |
| Models | 0 new · 2 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 e8f948eb960e.
The apps.odoo.com catalogue has a listing under the same technical name on 19.0: apps.odoo.com/apps/modules/19.0/project_hr_expense_analytic. A matching name does not prove matching code — how we counted this.
Depends on
| Module | Status | Checked |
|---|---|---|
| project_hr_expense | core | ships with Odoo |
Result looks wrong? Tell us — we will show the log or run it again. Report a wrong result