Changes between Version 15 and Version 16 of CodeReviewerPlugin
- Timestamp:
- May 24, 2012, 1:17:48 PM (12 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
CodeReviewerPlugin
v15 v16 110 110 }}} 111 111 112 In the above example, a "complete" ticket is now defined as not only having all changesets reviewed and the last review PASSED, but also that the ticket's custom phase field has a value of either codereview, verifying, or releasing.112 In the above example, a "complete" ticket is now defined as not only having all changesets reviewed and the last review PASSED, but also that the ticket's custom phase field has a value of either "codereview", "verifying", or "releasing". 113 113 114 114 The format of the completeness {{{trac.ini}}} options is a comma-delimited list of field-rule pairs where a rule is a regex that is used to match the field's value. … … 116 116 117 117 === Workflow - ticket changes === 118 You can have code review submissions automatically change fields of completed tickets. Continuing the workflow example from above, if a ticket's custom phase field gets set to "codereview" and reassigned to a reviewer, the reviewer may typically send the ticket back to "implementation" and the author after thereview. The plugin can do this automatically via specifying this in {{{trac.ini}}}:118 You can have code review submissions automatically change fields of completed tickets. Continuing the workflow example from above, if a ticket's custom phase field gets set to "codereview" and reassigned to a reviewer, the reviewer may typically send the ticket back to "implementation" and the author after a failed review. The plugin can do this automatically via specifying this in {{{trac.ini}}}: 119 119 {{{ 120 120 [codereviewer]