How to limit user's ability to self-approve in the formal review section?
Accepted answer
Hi Nick,
Currently there is no way to do that. Any user is able to go to an artifact and claim that it needs to be reviewed by himself by adding an approval with its own user. In the other side, it is an interesting item to be considered in our advisors.
Thought: you could add required approvals of a certain type of user (i.e. test leader) on the project area configuration to restrict approved states of artifact using normal users (i.e. test team members) approvals.
Currently there is no way to do that. Any user is able to go to an artifact and claim that it needs to be reviewed by himself by adding an approval with its own user. In the other side, it is an interesting item to be considered in our advisors.
Thought: you could add required approvals of a certain type of user (i.e. test leader) on the project area configuration to restrict approved states of artifact using normal users (i.e. test team members) approvals.
Comments
Thank you for the response and suggested alternative.
I'm going to open an RFE to request this functionality.
We like to have all our experienced testers involved in the review process. Restricting the approvals to leads only could cause a bottleneck effect and delayed approvals, or hasty approvals that overlook an error.
I have considered adding a precondition to require two approvals so that no individual can be the sole approver of their own work. This option is not perfect, and it creates extra work for the end user; who now has to add two approvers and approve the artifact himself.