I don't really know if I have chosen the right category, but I didn't found something for "rights concept". So, to add this category is my first suggestion. :-)

But my real issue is: I like to suggest a closer relation between a status change and the user's role.

Imagine the following simple worklfow:
new - under developement - test - solved

So we have users that do report an issue (reporters) and therefore produce issues of status "new". These very same people shall test what they requested (e.g. in support desks this is a typical situation "can you please check if it is working now?"). So, if the test is positive they change the status to "solved", and if the test is negative they change the status back to "under development". BUT, with current configuration possibilities this always includes that the reports are able to assign issues to the developpers as they have the right to set this status (back from test) and obviously the status matrix allows the change from "new" to "under developement".

So, my suggestion is to set the roles instead of just true/false-flags in the workflow matrix (ie you have the dropdown box with all user roles instead of the checkboxes). This way you can define that a status change from "new" to "under development" is possible for let's say managers only, but back from test to dev is even possible for reporters.

This way some of the options under the threshold dialog become obsolete. You don't need the option anymore that "a reporter can close issues" because you set this directly in the workflow matrix. So we are also talking about a cleanup of the threshold configuration that looks to be a bit "historically grown" or distributed over the system... :-)