# Feature OP-11536 - Project status activity tracking

Project: OpenProject
Status: closed
URL: https://community.openproject.org/work_packages/OP-11536

## Planning

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | Medium |
| Target versions | 13.0.0 |
| Sprint | 13.0.0 |
| Backlog bucket |  |
| Votes | 2 |
| List |  |
| Roadmap |  |
| Relevance |  |

## OPEN POINTS / FEEDBACK

_No work packages_

## Features and Chunks

| ID | Subject | Type | Status | Assignee | Target versions | Spent time |
| --- | --- | --- | --- | --- | --- | --- |
| OP-12470 | Include the status code and explanation into the journals (and projects table)  | Implementation | closed |  | 13.0.0 |  |
| OP-12471 | Support project status changes when rendering project activity | Implementation | closed |  | 13.0.0 |  |
| OP-12472 | Support project status explanation changes when rendering project activity | Implementation | closed |  | 13.0.0 |  |

## Bugs and other work packages

_No work packages_

## Technical Details

| Attribute | Value |
| --- | --- |
| Module |  |
| Feature Flag |  |
| Requires doc change | No |
| Enterprise plan |  |

## Details

| Attribute | Value |
| --- | --- |
| Pull preview |  |
| Mockups |  |
| Found in mobile app version |  |
| Follow-up feedback e-mail |  |
| Accessibility | No |

## People

| Attribute | Value |
| --- | --- |
| Assignee | Niels Lindenthal |
| Accountable | Jens Ulferts |
| Product manager |  |
| Developers |  |
| Designer | Parimal Satyal |
| Ordered by | Harald Herz |
| Signed off by | Harald Herz |
| Interest by |  |

## Estimates and progress

| Attribute | Value |
| --- | --- |
| PD (min) |  |
| PD (max) |  |
| Work | 20d 0h · Σ 20d 0h |
| Labor costs |  |

## Description

**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 <mention class="mention" data-id="43852" data-type="work_package" data-text="#43852">#43852</mention>). 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** set to *{status}*"
      - When initially providing a status explanation
          - **"Project status** **description** set ([Details](https://community.openproject.org/#))" with a link to the diff view similar to the diff view of the project description
      - When changing the code
          - "**Project status** changed from *{old status}* to *{new status}*"
      - When changing the status explanation
          - e.g. '**Project status description** changed ([Details](https://community.openproject.org/#))' 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** deleted (*~~{Old project status}~~*)'
      - When removing the status explanation
          - e.g. '**Project status description** deleted ([Details](https://community.openproject.org/#))''

**Prerequisites**

  - can only be implemented after <mention class="mention" data-id="43852" data-type="work_package" data-text="#43852">#43852</mention>