Content
View differences
Updated by Parimal Satyal about 3 years ago
**As** a project administrator
**I want to** have the changes to the project status journalized
**so that** I can understand the history of the project
**Acceptance criteria**
* Include the project status properties in the project journalization. Whenever a change is made to the following fields, a journal is created in the database:
* code (e.g. "on track", "at risk")
* explanation
* Display the changes to the project status together with the rest of the project attributes on the project's activity view (see #43852). The changes will be displayed as a flat list, meaning that the changes to code and explanation that could happen at the same time will not be displayed together but as separate changes within the list of all the changes done the the project in the aggregated timeframe.
* When initially setting a code
* **"Project status** e.g. 'Project status set to _{status}_" "on track"'
* When initially providing a status explanation
* **"Project status** **description** e.g. 'Project status explanation set ([Details](https://community.openproject.org/#))" (Details)' with a link to the diff view similar to the diff view of the project description
* When changing the code
* "**Project status** changed e.g. 'Project status changes from _{old status}_ "on track" to _{new status}_" "at risk"'
* When changing the status explanation
* e.g. '**Project 'Project status description** explanation changed ([Details](https://community.openproject.org/#))' (Details)' with a link to the diff view similar to the diff view of the project description
* When removing the status code
* e.g. '**Project status** 'Project status deleted'
* When removing the status explanation
* e.g. '**Project 'Project status description** explanation deleted'
**Prerequisites**
* can only be implemented after #43852
**I want to** have the changes to the project status journalized
**so that** I can understand the history of the project
**Acceptance criteria**
* Include the project status properties in the project journalization. Whenever a change is made to the following fields, a journal is created in the database:
* code (e.g. "on track", "at risk")
* explanation
* Display the changes to the project status together with the rest of the project attributes on the project's activity view (see #43852). The changes will be displayed as a flat list, meaning that the changes to code and explanation that could happen at the same time will not be displayed together but as separate changes within the list of all the changes done the the project in the aggregated timeframe.
* When initially setting a code
* **"Project status**
* When initially providing a status explanation
* **"Project status** **description**
* When changing the code
* "**Project status** changed
* When changing the status explanation
* e.g. '**Project
* When removing the status code
* e.g. '**Project status**
* When removing the status explanation
* e.g. '**Project
**Prerequisites**
* can only be implemented after #43852