subtask_counter

A task with sub-tasks has a progress story that its own stage does not tell. Four of six done is a different situation from one of six, and both look identical if the row only shows a stage.

This widget puts that ratio on the row: closed over total, in a form compact enough for a list column. It also serves as the control for expanding the sub-tasks underneath, so the number and the way to see the detail are the same target.

The compact display is paired with a spelled-out title, so the meaning is available to anyone who cannot infer it from two numbers and a slash.

Sub-tasks are how most teams model work that is too big for one row and too small for its own project. The failure is that the parent's status stops reflecting reality, and everyone starts opening tasks to find out where things stand.

A visible ratio on the list fixes that at the cheapest possible point. What it does not fix is sub-tasks being used where a checklist would do, which is worth a conversation before the hierarchy gets deep.

Placing it

<widget name="subtask_counter"/>

Inside the task list. No attributes.

What is displayed

2/6

Closed over total.

What the title says

2 sub-tasks closed out of 6

The spelled out form, for accessibility.

There are four getters and one handler, and none of them do anything clever, which is the right outcome for a list cell rendered hundreds of times.

Two getters read the counts straight from the record. Two more build strings: the compact display and the longer title, both translatable with named placeholders so translators can reorder them.

The handler calls a method on the record that toggles the nested sub-task list. Delegating rather than keeping local state is what makes the widget correct when the same task appears twice, or when the list is re-rendered.

The field dependencies are the last piece. Requesting both counts means the numbers are present even in a list that does not include those columns, which is the normal case since the widget replaces them.

Odoo 20 is expected at Odoo Experience in Brussels, 24 to 26 September 2026. The development branch is unstable and this may still change; we re-verify this page after the release.

Byte-identical. The file on the development branch matches Odoo 19 exactly, including both translatable strings.