# Feature OP-13638 - Allow status change without Edit WP rights

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

## Planning

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

## OPEN POINTS / FEEDBACK

_No work packages_

## Features and Chunks

_No work packages_

## Bugs and other work packages

| ID | Type | Subject | Status | Assignee | Target versions | Spent time | Module |
| --- | --- | --- | --- | --- | --- | --- | --- |
| OP-14110 | Bug | Status cannot be changed in backlogs when only having change_work_package_status permission | closed |  | 13.2.0 |  |  |
| OP-14109 | Bug | lockVersion missing in payload for API WP form when only having change_work_package_status permission | closed |  | 13.2.0 |  |  |

## Technical Details

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

## Details

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

## People

| Attribute | Value |
| --- | --- |
| Assignee |  |
| Accountable |  |
| Product manager |  |
| Developers | Richard Richter |
| Designer |  |
| Ordered by |  |
| Signed off by |  |
| Interest by |  |

## Estimates and progress

| Attribute | Value |
| --- | --- |
| PD (min) |  |
| PD (max) |  |
| Work |  |
| Labor costs |  |

## Description

**As** a customer (role)  
**I want to** change the status (according to the workflow set for the role)  
**so that** I can, for example, close (accept) or reopen (reject) the WP, or execute any other status change without asking for it via comment.

Technically, this would be realized with a separate permission `change_work_package_status` and the solution would be an analogue to the existing `add_work_package_attachments` permission.

### **Acceptance criteria**

  - User with the role having `change_work_package_status` permission sees WP Status as editable and can change it.
  - This should work also in tables, just as any other in-place edit.
  - Similar to `add_work_package_attachments` (and contrary to `assign_versions`), users with `edit_work_packages` will still be able to change the status, regardless of them having the `change_work_package_status` permission.
  - On the front-end, on the permissions page for each relevant role:
      - Add a new permission with label: "Change work package status"
      - Add guideline text underneath (similar to 'Add attachments'): "Allows changing status without Edit work packages permission"

I discussed this with <mention class="mention" data-id="9177" data-type="user" data-text="@Oliver Günther">@Oliver Günther</mention> previously, this can be eventually solved by <mention class="mention" data-id="27846" data-type="work_package" data-text="#27846">\#27846</mention> but that is not expected very soon. I will contribute this feature. Status is also special enough to warrant a separate permission, which would otherwise be cumbersome for every single other field.

The main reason is to allow our clients/contributors/etc. to not only comment that something is accepted/tested, or not acceptable/reopen, but also directly perform such a change, so we can see the WP in the right right away.

### **Out of scope**

  - When "Edit work packages" is checked:
      - Automatically check and disable "Change work package status"
      - Automatically check and disable "Add attachments"
  - When "Edit work packages" is unchecked:
      - Enable "Change work package status" but keep it checked
      - Enable "Add attachments" but keep it checked