Project Task Stage Auto State
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)
Table of contents
Use Cases / Context
This module is useful in workflows where tasks need to be automatically closed after a certain period of time in a stage.
Common use cases:
Auto-done: Approval workflows where silence means consent after N days
Auto-done: Service level agreements (SLA) with automatic closure when completed
Auto-cancel: Timeout periods where tasks expire if no action is taken
Auto-cancel: Cleaning up stale tasks in waiting or review stages
Usage
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
Bug Tracker
Bugs are tracked on GitHub Issues. In case of trouble, please check there if your issue has already been reported. If you spotted it first, help us to smash it by providing a detailed and welcomed feedback.
Do not contact contributors directly about support or help with technical issues.
Credits
Contributors
Maintainers
This module is maintained by the OCA.
OCA, or the Odoo Community Association, is a nonprofit organization whose mission is to support the collaborative development of Odoo features and promote its widespread use.
Current maintainers:
This module is part of the OCA/project project on GitHub.
You are welcome to contribute. To learn how please visit https://odoo-community.org/page/Contribute.
1 maintainer
Metadata
1 maintainer
Release files for odoo-addon-project-task-stage-auto-state 20.0.1.0.0.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| odoo_addon_project_task_stage_auto_state-20.0.1.0.0.3-py3-none-any.whl | Python 3 | none | any | Details for odoo_addon_project_task_stage_auto_state-20.0.1.0.0.3-py3-none-any.whl |
Release files / odoo_addon_project_task_stage_auto_state-20.0.1.0.0.3-py3-none-any.whl
| Download URL | odoo_addon_project_task_stage_auto_state-20.0.1.0.0.3-py3-none-any.whl |
|---|---|
| Size | 38.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
6427990f7275d83f8b4008f2f8e2f7bebb719babe42293590400cfb0c0df9101
|
|
BLAKE2b-256 checksum How to use checksums |
448948d9fd4335304b817524ab78f3fe838931e9ed06115d4b8209f5e2554c9f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.4
|
Security for odoo-addon-project-task-stage-auto-state 20.0.1.0.0.3
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
