Open link in a new tab

Content

Expand project menu

View differences

**Use Case:**

**Only defined users can move a work package from one status to another**, based on their role, group, permission, or their relation to the work package (assignee, author, or a user named in a field such as "Approver")

Example: If a user without the role "Developer" opens a work package in status "On Hold" the status change to "In Progress" will not be available to this user.

<br>

**User Story:**

As an admin, I want to define who may make a status change, so that only the responsible people can move work packages forward.

<br>

**Acceptance criteria**

1. Existing transitions per role, type, author and assignee keep working unchanged (_Note: We might want to make this clearer.)_

2. In addition, an admin can restrict a status change to a group, _a a permission (?)_ or a user named in a user custom field, such as Approver or Reporter

3. If several restrictions apply to one status change, all of them must be met

4. If the change to &quot;Approved&quot; is restricted to the user in the field &quot;Approver&quot;, other users don&#x27;t see &quot;Approved&quot; as an option

5. If the user named in &quot;Approver&quot; opens the work package then they can set it to &quot;Approved&quot;

6. The rules apply everywhere a user can change a status: work package view, tables, boards, boards and bulk edit, team planner. edit.

7. Status changes through an API (like scripts or integrations) follow the same rules as changes made by users


<br>

Open Question:

* In Jira, a workflow can say only members of group X and this works in every project automatically. In OpenProject, workflows use roles, so the group also has to be added to each project with the right role. Is this extra step acceptable or do we need &quot;group&quot; as its own restriction?

* What happens when the referenced user field is empty: nobody can make the change, or only admins, or not allowed to be empty?

* do we need OR combinations?

Back