Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,463,395
Community Members
 
Community Events
176
Community Groups

Crucible: enforce minimum number of reviewers?

Is there a way to enforce that a crucible review must have at least one reviewer? Our current set up allows someone to create and close a review without actually having the code changes reviewed, which isn't ideal.

We want to keep the review creator as the author of the changes; this makes sense, because only the author knows when the changes are ready for review. I think though, this means we can't use the moderator role to enforce that there is a reviewer, because the moderator is the creator? It would make more sense if the moderator was one of the reviewers but then we go back to how to enforce that there is at least one reviewer...

1 answer

1 accepted

0 votes
Answer accepted
Nick Atlassian Team Sep 10, 2013

Hi Helen,

You can configure a default reviewer (or reviewers) for each Project. Each review created in that project will then have this reviewer automaticall added. While the author can then remove this reviewer via the UI, it would mean they are conciously doing so, and I would suggest you need to seriously talk to that developer about why they created a review with no reviewers on it. It is essentially deciet.

Apart from doing spot-checks and ensuring you have a healthy team culture, where developers are doing the right thing, you could write a crucible plugin which enforces that each review created has at least one reviewer on it. It could be possible however for developers to still game this via other means, so I think its best to trust and then verify that developers are doing the right thing.

Crucible provides some very good reports which let you as a manger see at a glance whether or not reviews are being created without any reviewers. e.g. go to : /cru?filter=allReviews and see the last column.

Cheers,

Nick

Default reviewers will be close enough I think. Thanks very much!

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events