OdooWiki OCA HUB

Project Task Stage Auto State

project_task_stage_auto_state folder_open OCA/project open_in_new
Productivity/Project License: LGPL-3

Automatically change task state (done or canceled) after they remain in a stage for a configured number of days.

Key features:

  • Configure auto-done days per stage with states that you want to apply.
  • Configure auto-cancel days per stage with states that you want to apply.
  • Automatic message posted in task chatter
  • Daily scheduled action to process tasks
  • Only open tasks are processed (closed states are ignored)

auto_awesome What this module does

AI-generated from the code · Odoo 19.0

Automatically mark project tasks as done or canceled after they stay too long in a stage. Configure the number of days and which task states are allowed per stage.

This module adds automatic housekeeping for project tasks. On each task stage (the columns of your Kanban board), you can now set a number of days after which tasks still sitting there should be closed.

  • 'Auto-mark as done after days': tasks left in the stage for that many days are marked as done.
  • 'Auto-cancel after days': tasks left in the stage for that many days are canceled.
  • For each option you tick which starting states are allowed (In Progress, Changes Requested, Approved, Waiting). Tasks already done or canceled are never touched.

These settings appear in the stage configuration form, in two groups called Auto-Done and Auto-Cancel, and as optional columns in the stage list. Odoo refuses to save a stage where a number of days is set but no starting state is ticked, and negative day values are blocked.

A daily scheduled action runs in the background, checks every stage with a configured delay, and closes the matching tasks. Each affected task receives a note in its chatter explaining that it was automatically done or canceled, after how many days and in which stage. If both rules could apply to the same task, done wins over cancel.

Depends on

project
Models and fields (2)
  • project.task · extends an existing model
  • project.task.type · extends an existing modelauto_done_days (Auto-mark as done after days), auto_cancel_days (Auto-cancel after days), allow_done_from_waiting (Allow Done from Waiting), allow_done_from_approved (Allow Done from Approved), allow_cancel_from_waiting (Allow Cancel from Waiting), allow_cancel_from_approved (Allow Cancel from Approved), allow_done_from_in_progress (Allow Done from In Progress), allow_cancel_from_in_progress (Allow Cancel from In Progress), allow_done_from_changes_requested (Allow Done from Changes Requested), allow_cancel_from_changes_requested (Allow Cancel from Changes Requested)

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-03
Confirmed (verified in repository and branch) Estimated (unverified) No information

Confirmation status: 2 confirmed, 7 with no information of 9 versions.

terminal Installation and usage

OCA documentation · Odoo 19.0

To use this module, you need to:

  • Enter debug mode
  • Go to Project > Configuration > Task Stages
  • Select or create a stage
  • Configure the automatic actions:
  • Set "Auto-mark as done after days" to the desired number of days (0 to disable)
  • Activate shown boolean fields for states that you want to do something
  • Set "Auto-cancel after days" to the desired number of days (0 to disable)
  • Activate shown boolean fields for states that you want to do something
  • Verify that the scheduled action "Project: Auto-change task state by stage" is active in Settings > Technical > Automation > Scheduled Actions
  • When a task is auto-changed, a message is posted in the chatter indicating the automatic action

Notes:

  • The counter starts from the "Last Stage Update" date, which is updated each time a task changes stage
  • If both auto-done and auto-cancel are configured for the same stage and both thresholds are reached, auto-done takes precedence

No verified information in OCA: Installation, Configuration.

info

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.