The entire idea behind the suggestion is to create a proper workflow for Review Trainees. With as little manual intervention as possible, we need a way to:<div><br></div><div>1) Assign a ticket to a Reviewer Trainee (requires a "Reviewer Trainee" user group, with appropriate permissions)</div>
<div>2) Have Reviewer Trainee review ticket, leave review comments, and close/resolve the ticket (requires Reviewer Trainee-specific ticket resolutions)</div><div>3) Alert a Reviewer that a Reviewer Trainee has completed a review that requires an audit (requires custom reports based on Reviewer Trainee-specific ticket resolutions)</div>
<div>4) Have a Reviewer audit the ticket, and close/resolve appropriately, confirming (or not) the suggested resolution</div><div><br></div><div>Having user-group specific ticket resolutions would create systemic controls over the process, thus requiring less manual intervention. In any case, we can surely implement the Reviewer Trainee user group, and suggest-approval/suggest-not-approval ticket resolutions. We would just have to rely on *telling* the Reviewer Trainees only to use the "suggest-" resolutions, and auditing to ensure that they follow those instructions.</div>
<div><br></div><div>This will also help clarify (or redefine) the use of "suggest-approval" and "needs-additional-review" - one of which can be removed, depending on which way we choose to go.</div><div>
<br></div><div>Chip</div><div><br><br><div class="gmail_quote">On Fri, Oct 8, 2010 at 10:16 AM, Edward Caissie <span dir="ltr"><<a href="mailto:edward.caissie@gmail.com">edward.caissie@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Although I would like to know more behind these ideas Chip ... I do like the idea of the "suggest-not-approved" resolution, it could even replace the "needs-additional-review" resolution.<br>
<br>BUT, each resolution needs to be clearly defined, or at least defined well enough so it is easily understood when to use; and, what is required when using each.<br>
<br><br>Cais<br><br><div class="gmail_quote"><div><div></div><div class="h5">On Fri, Oct 8, 2010 at 10:42 AM, Chip Bennett <span dir="ltr"><<a href="mailto:chip@chipbennett.net" target="_blank">chip@chipbennett.net</a>></span> wrote:<br>
</div></div><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204, 204, 204);padding-left:1ex"><div><div></div><div class="h5">
Otto/Nacin,<div><br></div><div>Is it possible to restrict Trac ticket resolution options by user group? For example, can Group A be restricted to Resolution 1 and Resolution 2, while Group B is restricted to Resolution C and Resolution D?</div>
<div><br></div><div>If so, would it be possible to implement the following for Theme-Trac?</div><div><br></div><div>New User Group: Review Trainee</div><div><br></div><div>Ticket Resolution Permissions:</div><div><br></div>
<div> - approved (Reviewer, Review Admin)</div><div> - not-approved (Reviewer, Review Admin)</div><div> - suggest-approval (Review Trainee)</div><div> - suggest-not-approved (Reviewer Trainee)</div><div> - DELETE needs-additional-review</div>
<div><br></div><div>Alternately (a decision for Cais/Pross, I think):</div><div><br></div><div> - approved (Reviewer, Review Admin)</div><div> - not-approved (Reviewer, Review Admin)</div><div> - needs-additional-review (Review Trainee)</div>
<div> - DELETE suggest-approval</div><div><br></div><div>Thoughts? Is this possible?</div><div><br></div><font color="#888888"><div>Chip</div>
</font><br></div></div><div class="im">_______________________________________________<br>
theme-reviewers mailing list<br>
<a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">theme-reviewers@lists.wordpress.org</a><br>
<a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a><br>
<br></div></blockquote></div><br>
<br>_______________________________________________<br>
theme-reviewers mailing list<br>
<a href="mailto:theme-reviewers@lists.wordpress.org">theme-reviewers@lists.wordpress.org</a><br>
<a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a><br>
<br></blockquote></div><br></div>