@ganncamp thank you for your reply. It does not help me.
I need a permission that completely restrict developers to mark issues as resolved. They should not be able to see the {Resolve as fixed, Resolve as false positive, Resolve as won’t fix} options.
The QA team has Administer Issues permission set up. They are able to mark an issues as fixed.
If the developers will have only browse permission, they will be able to mark issues as fixed as well.
I’ve added an image with the view that a developer has. I mention that the developers have browse permission, because the project is set up as private and without this permission, they are not allowed to see the project.
I understand the confusion now. “Resolve as fixed” is a temporary marker to say “I’ve worked on the code and I believe the next analysis will Close this issue”. But it’s not a permanent marker; and the next analysis will actually Reopen the issue if it hasn’t actually been fixed.
Unfortunately, with the introduction of Live Measures a couple versions ago, this resolution does have an immediate impact on issue counts and therefore potentially the Quality Gate, but those impacts only last until the next analysis.
There’s no permission that controls access to this action because it’s not permanent. Also, we have plans to remove the action, altho I can’t give you an ETA on that.