Changes between Version 15 and Version 16 of CodeReviewerPlugin


Ignore:
Timestamp:
May 24, 2012, 3:17:48 PM (3 years ago)
Author:
robguttman
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • CodeReviewerPlugin

    v15 v16  
    110110}}}
    111111
    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.
     112In 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".
    113113
    114114The 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.
     
    116116
    117117=== 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 the review.  The plugin can do this automatically via specifying this in {{{trac.ini}}}:
     118You 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}}}:
    119119{{{
    120120[codereviewer]