Review Templates

Why use review template?

Review templates essentially act as reminiscent checklists for reviewers during code reviews and release managers during accpetance tests.
Review templates are usually compiled from common problems found during failed reviews or acceptances. You can filter them out on relevant history screen.

Review template is a custom fill-in form with criteria on the rows and possible values in columns. Both criteria and possible values are user-definable. The review templates are defined separately for every project; change review templates are further separated by change reason. For example, a review template criteria could be “Access control checks are correct” and “Error handling is correct” with values “yes” and “no” .

The template has to be filled in when ending review or acceptance, assuming a relevant template has been defined. Negative answers on a review template do not prohibit failing the review/acceptance, nor do positive answers force passing it. The template simply reminds some common things to check for and records results for future reference.
NOTE: when review or acceptance is not ended when saving change/version details form, the results filled in the template are not saved, although the template was present.

Read more about how to define review templates from dedicated page.