Issue permissions per Category

[anna_wahlsten]

We need to be able to give different Issue permissions depending on the Issue category. For example, we need the CDM principle designer to be able to edit all issues raised under the category CDM, which will be created by the rest of the design team. We do not want to give full edit powers, as there are certain issue categories such as Cost where we need to restrict visibility. We currently don't have a way around this. This limits the usability of Issues and steers people away from managing all project related issues in one space as they cannot be managed properly.

[jmeuris]

It is true that issue permission could be improved.

For the time being, if you create a new issue, try to assign not one person, but a role, then all people assigned to that role will receive a notification and can follow up and/or address it. Furthermore, it will avoid the problem when somebody is OoO, nobody follows it up and it gets delayed.

[anna_wahlsten]

My suggestion is not related to assigning an issue to someone, but about who can edit the metadata within an issue, beside its creator. The assignee can only edit the status or the assigned to fields. We are asking for more flexibility on issue management so that responsible parties of different categories can manage their issues more effectively while maintaining other restrictions.