The module restores the possibility of defining analytical tags in project tasks and timesheets so that the analytical items generated have those tags.
auto_awesome What this module does
AI-generated from the code · Odoo 18.0Lets you set analytic tags on a project task so that timesheets recorded on that task automatically inherit those tags on their analytic entries.
This module adds a new field called Analytic Tags to project tasks. You can find it on the task form, right after the task image field, and it is only visible to users who belong to the analytic tags group. The field uses a tag-style selector and only offers tags that belong to the same company as the task (or tags shared across companies).
When a timesheet or other analytic entry is created with a link to a task and no tags of its own, the module automatically copies the tags defined on that task onto the analytic entry. This means the analytical items generated from timesheets carry the same tags as the task, without users having to enter them again.
- Adds an Analytic Tags field on
project.task. - On creation of an
account.analytic.linelinked to a task, if no tags are set, the task's analytic tags are applied automatically. - The field is restricted to the analytic tags user group and respects company rules.
It touches the project task screen and the analytic line records used by timesheets. No new menus, reports or scheduled actions are added.
Depends on
Models and fields (2)
- project.task · extends an existing modelanalytic_tag_ids (Analytic Tags)
- account.analytic.line · extends an existing model
Text generated by AI (DeepSeek) from reading the Odoo 18.0 code on GitHub; it may contain mistakes, so check the code before deciding. View the code on GitHub
Availability by version
Reviewed: 2026-11-03Confirmation status: 3 confirmed, 6 with no information of 9 versions.
Sources · Odoo 18.0
Confirmed on 2026-11-03 in branch 18.0 of OCA/account-analytic.
terminal Installation and usage
No verified informationInstallation instructions, the distribution package, dependencies and configuration steps are not shown because they have not yet been verified in the module documentation for any version.
Data imported from GitHub: this sheet reflects the latest catalog review, not a live lookup. Always check the module documentation and staging before installing in production.