### Steps to reproduce

Begin of the insertion* End of the insertion Begin of the deletion 1. End of the deletion Configure Begin of the insertionthe workflowEnd of the insertion Begin of the deletion strict state change restrictions limiting actions to assigneeEnd of the deletion for Begin of the insertiona work package ofEnd of the insertion Begin of the deletion issueEnd of the deletion type Begin of the insertionT and role R so that only assignees can do a status change. No change should be configured in the general section. It might then e.g. look like this:
<img class="image_resized op-uc-image op-uc-image_inline" style="width:251px;" src="/api/v3/attachments/792903/content">End of the insertion Begin of the deletion XEnd of the deletion

Begin of the insertion* Have aEnd of the insertion Begin of the deletion 2. Assign issue type X with assignee set toEnd of the deletion group Begin of the insertionGEnd of the insertion Begin of the deletion ofEnd of the deletion which Begin of the insertionhas theEnd of the insertion user Begin of the insertionU as its member

* Assign the group G to beEnd of the insertion Begin of the deletion Y isEnd of the deletion a member Begin of the insertionof a project with work packages of the type T. Grant it the role R. It should not have any other role (for easier reproducibility, not because it triggers the bug).End of the insertion

Begin of the insertion* GoEnd of the insertion Begin of the deletion 3. As user Y, attemptEnd of the deletion to Begin of the insertiona work package of type T.

* Change the assignee to the group G.

* Try to change the status.End of the insertion Begin of the deletion progress stateEnd of the deletion


### What is the buggy behavior?

Begin of the deletion _Please describe the bug in as much detail as possible. Example:_

End of the deletion * No status change options are available to a member of the assigned group when only the assignee can change status

* Users have to self-assign the issue to make state change which removes notifications of said change for all members of actually assigned group Begin of the insertion


End of the insertion Begin of the deletion

* (tagging as high priority because) Adversely impacts GRC workflows around change control/decision-tracking


End of the deletion ### What is the expected behavior?

Begin of the deletion _Describe how the application should behave like. Example:_

End of the deletion 1. Group membership is resolved to ascertain whether user Begin of the insertionUEnd of the insertion Begin of the deletion YEnd of the deletion as member of the group Begin of the insertionU havingEnd of the insertion Begin of the deletion hasEnd of the deletion permission to make status change on issue type Begin of the insertionTEnd of the insertion Begin of the deletion XEnd of the deletion


**OpenProject version**

_v15.2.0_