Content
Updated by Richard Richter almost 2 years ago
**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 `assign_versions` permission.
**Acceptance criteria**
* User with the role having the `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 `assign_versions`, user with `edit_work_packages` will NOT be able to change the status, unless they also have `change_work_package_status` permission. Migration adding the new permission for roles with edit WP rights will be provided.
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 be 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.
**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 `assign_versions` permission.
**Acceptance criteria**
* User with the role having
* This should work also in tables, just as any other in-place edit.
* Similar to `assign_versions`, user with `edit_work_packages` will NOT be able to change the status, unless they also have `change_work_package_status` permission. Migration adding the new permission for roles with edit WP rights will be provided.
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
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.