Add ability to specify reason or reasons for commenting on a code diff
Description
Right now, there is no easy way to generate analytics based on code review comments. Being able to generate analytics based on code review comments can be useful, since they can be used to help you determine:
- How complex the code in the source file is.
- How a particular programmer is performing.
- How entangled the code in the source file is.
and so forth
Proposal
Make it possible for people to define custom code review tags, that can be attached any code review comment. For example, make it possible for people to create custom tags like:
- Spelling error
- Logic error
- Broken by downstream change
- Incomplete fix
and so on.
By making it possible for reviewers to easily specify their reason or reasons for commenting, you can generate useful analytics, that can help you better predict future defect risks and other software quality related questions.