maybe I misunderstood the permission “Block a release from progressing to the next lifecycle phase (restrictable to projects)”, so please correct me if I’m wrong, thx.
I have the following setup:
- I added a specific user to a new team.
- The team has the “System administrator” role with the “Block a release …” permission
- No other restrictions like Projects or Environments are set.
- I login with the credentials of that user and I see the “Block option” in the overview page of an arbitrary release.
- I logout
- I change the permissions for the team so that they are limited to a specific project.
- I login with the credentials of that user and I DO NOT see the “Block option” in the overview page of a release for the specific project.
Isn’t it supposed to work this way?
The usage scenario is that certain members of a QA team should have the “Block a release …” permission but limited to both certain projects and certain environments, so they can prevent a “bad” release from being propagated to a later stage.
Also the “System administrator” role is the only viable role to accomplish this usage scenario, right? I personally think that another role with less permissions or maybe the options to select permissions indicidually rather than complete roles would be desirable, but let’s not get things mixed up and concentrate on the original question.
Thx in advance!