Issue 1187: Allow reviewer to be tagged with a reason for being added as a reviewer
Status:  New
Owner: ----
Reported by bofferd...@gmail.com, Nov 15, 2011
It would be nice to be able to tag each assigned reviewer with a review priority, such as:

- FYI only; no actual expectation of review
- Review is considered optional for given reviewer
- Review is considered mandatory for given reviewer (with potential interlocks to prevent code from being submitted without review from this reviewer)

The concept could be extended with separate, configurable, stackable tags to indicate why the reviewer might have an interest in performing the review, such as:

- Code the reviewer directly owns is being modified
- Reviewer has specific, helpful expertise in some aspect of the code (such as how to implement a tricky algorithm) 
- Reviewer is a gatekeeper of code being admitted to a repo
- etc.

In our organization, lots of reviewers are added to code reviews for all the above cited reasons (and more), but without follow-up notes, it is difficult to convey expectations, priorities, etc. Reviewers can even be confused why they were asked to review in the first place.

Jul 16, 2015
#1 namrata....@gmail.com
To be more specific, it would be very helpful if we could have separate fields such as:

Primary reviewer:
Secondary reviewers:
Approver (or Gate-Keeper):
Verifier:
FYI-Only:

It would also be helpful to have a "Waiting-On" field. This could be used to tag a specific person that needs to look at a given patchset. Often, 1 of the 5 reviewers will comment, then the author will update the review based on those comments. So now the ball is in Reviewer1's court. This should be possible to indicate clearly.
Jul 16, 2015
#2 namrata....@gmail.com
Also, once this is implemented, there should be a way to categorize your dashboard based on your role. E.g. a section for all patches for which you are primary reviewer, a separate section for all patches where you are the verifier, and so on.