Launch: Help us enforce maker/checker process

Avatar

Avatar
Shape 100
MVP
AndrewWathen
MVP

Likes

574 likes

Total Posts

320 posts

Correct reply

15 solutions
Top badges earned
Shape 100
Bedrock
Springboard
Seeker
Contributor
View profile

Avatar
Shape 100
MVP
AndrewWathen
MVP

Likes

574 likes

Total Posts

320 posts

Correct reply

15 solutions
Top badges earned
Shape 100
Bedrock
Springboard
Seeker
Contributor
View profile
AndrewWathen
MVP

08-02-2018

Currently, the following roles are available:

  • develop
  • approve
  • publish

I want to be able to stop people approving code that they have developed themselves.  However, our team is not big enough that we can afford to have mutually exclusive groups of developers and testers.  Therefore, I have to give 'develop' and 'approve' rights to everyone, which mean users can effectively mark their own homework.

What I would like is an additional 'approve' permission which only allows a user to 'approve' libraries submitted for approval by other users  i.e. they can 'approve' other peoples code for publishing, but not their own.