As we approve more Themes - and especially, Themes that are approved, but that have comments indicating certain issues are "Required, but Can Be Fixed in Next Revision" - I'm thinking that we might want to consider another ticket resolution: "approved-with-comments" or "approved-with-next-revision-fixes" or something along those lines.<div>
<br></div><div>The reason? I'm seeing tickets for "next revisions" of such tickets, that seem to ignore completely the issues indicated as "Required, but Can Be Fixed in Next Revision". </div><div>
Of course, I'm resolving such tickets as "not-approved" - but the reason I bring it up is that we haven't really discussed how we handle such tickets. </div><div><br></div><div>My process for a Priority #1 Queue ticket is:</div>
<div><br></div><div>1) Check previous-tickets report, to ensure ticket is in correct queue (Pross: can we get the *resolution* column to display by default on this report?)</div><div>2) If correct queue, assign ticket to myself</div>
<div>3) Open previous ticket, to check for any issues indicated as "Can Be Fixed in Next Revision"</div><div>4) Diff-Review</div><div>5) Theme-Check</div><div>6) Summarize status of previous-ticket comments</div>
<div>7) (if necessary) Install/check activated Theme</div><div>8) Close/resolve ticket</div><div><br></div><div>The problem I'm foreseeing, of course, is that the previous-ticket comments can very easily fall through the cracks, unless the next-ticket reviewer makes a conscious effort to check the previous ticket. We could alleviate this concern by introducing an appropriate ticket resolution, that would alert the next-ticket reviewer to the presence of any such previous-ticket issues.</div>
<div><br></div><div>Thoughts?</div><div><br></div><div>Chip</div>