Content
View differences
Updated by Niels Lindenthal 14 days ago
**As** an OpenProject user
**I want** OpenProject to do things automatically for me
**so that** I save time and energy.
## 1\. Inactivity reminder
Reminds users (e.g. assignee, author or reponsible persons) when a work package has not been updated for a defined period.
**Example**
If no update for 5 days:
**Comment**
```text
Hi @Assignee
This work package has not been updated for 5 days. Please add a short status update.
cc @Author, @Responsible
```
**Changed attributes**
* None, comment only
## 2\. Stale work package cleanup
Automatically closes abandoned work packages after a longer period of inactivity.
**Example**
If no update for 90 days:
**Comment**
```text
Hi @Assignee
This work package was automatically rejected because it has not been updated for 90 days.
cc @Watcher and @Author
```
**Changed attributes**
* Status → Rejected
* Priority → Low
## 3\. Escalation after missing status transition
Escalates work packages that remain too long in the same status.
**Example**
If status is unchanged for 14 days:
**Comment**
```text
Hi @Assignee
This work package has not changed status for 4 hours and was automatically escalated.
cc @Manager-of-Assignee
```
**Changed attributes**
* Priority → High
* Assignee → Manager of Assignee (taken from org-chart)
* Status → Escalated
## 4\. Automatic assignee selection
Assigns new work packages based on simple rules.
**Example**
If type is Bug and assignee is empty:
**Comment**
```text
Assignee was automatically selected based on the work package type "Bug".
```
**Changed attributes**
* Assignee → QA team
## 5\. Automatic due date management
Sets or adjusts due dates when workflow changes happen.
**Example**
If status changes to In progress:
**Comment**
```text
Due date was automatically set because the work package moved to "In progress".
```
**Changed attributes**
* Start date -> Current date
**I want** OpenProject to do things automatically for me
**so that** I save time and energy.
## 1\. Inactivity reminder
Reminds users (e.g. assignee, author or reponsible persons) when a work package has not been updated for a defined period.
**Example**
If no update for 5 days:
**Comment**
```text
Hi @Assignee
This work package has not been updated for 5 days. Please add a short status update.
cc @Author, @Responsible
```
**Changed attributes**
* None, comment only
## 2\. Stale work package cleanup
Automatically closes abandoned work packages after a longer period of inactivity.
**Example**
If no update for 90 days:
**Comment**
```text
Hi @Assignee
This work package was automatically rejected because it has not been updated for 90 days.
cc @Watcher and @Author
```
**Changed attributes**
* Status → Rejected
* Priority → Low
## 3\. Escalation after missing status transition
Escalates work packages that remain too long in the same status.
**Example**
If status is unchanged for 14 days:
**Comment**
```text
Hi @Assignee
This work package has not changed status for 4 hours and was automatically escalated.
cc @Manager-of-Assignee
```
**Changed attributes**
* Priority → High
* Assignee → Manager of Assignee (taken from org-chart)
* Status → Escalated
## 4\. Automatic assignee selection
Assigns new work packages based on simple rules.
**Example**
If type is Bug and assignee is empty:
**Comment**
```text
Assignee was automatically selected based on the work package type "Bug".
```
**Changed attributes**
* Assignee → QA team
## 5\. Automatic due date management
Sets or adjusts due dates when workflow changes happen.
**Example**
If status changes to In progress:
**Comment**
```text
Due date was automatically set because the work package moved to "In progress".
```
**Changed attributes**
* Start date -> Current date