This module allows to open and close tasks from account analytic lines. The selected closed stage is the first one that is found with the mark "Closed" checked.
auto_awesome What this module does
AI-generated from the code · Odoo 19.0Open or close the task linked to a timesheet entry directly from the timesheet line, without leaving the timesheet screen. The task is moved to the first stage marked as closed or to the first open stage of its project.
This module adds quick open/close controls to timesheet entries (task logs) so you do not have to open the task itself to change its stage.
In the timesheet list view, a small folder button appears next to the task on each line: a closed-folder icon to close the task and an open-folder icon to reopen it. The icon shown depends on whether the linked task is currently in a closed stage.
On the timesheet entry form, a status button in the top button box shows "Closed" or "Open" and toggles the task stage when clicked.
Business rules applied automatically: - Closing a task moves it to the first stage of its project that has the "Closed" mark checked. - Opening a task moves it to the first stage of its project that does not have the "Closed" mark checked. - If no suitable stage exists in the project, an error message asks you to mark at least one stage accordingly. - Lines without a task or without a project are simply ignored.
The module works on account.analytic.line records and only affects the task's stage; it does not change timesheet hours or other data.
Depends on
Models and fields (1)
- account.analytic.line · extends an existing modelis_task_closed
Text generated by AI (DeepSeek) from reading the Odoo 19.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: 8 confirmed, 1 with no information of 9 versions.
Sources · Odoo 13.0
Confirmed on 2026-11-03 in branch 13.0 of OCA/timesheet.
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.