[theme-reviewers] New Ticket Resolution
edward.caissie at gmail.com
Thu Oct 14 19:36:33 UTC 2010
If I'm understanding the basic idea behind "workflows" we can do more than
what we are seeing now in a "basic" Trac installaton.
Unfortunately it is not very intuitive, so I will be reading the wiki and
looking at the pretty pictures at least a few more times. (*grin*)
On Thu, Oct 14, 2010 at 2:44 PM, Otto <otto at ottodestruct.com> wrote:
> On Thu, Oct 14, 2010 at 1:35 PM, Chip Bennett <chip at chipbennett.net>
> > On Thu, Oct 14, 2010 at 1:32 PM, Edward Caissie <
> edward.caissie at gmail.com>
> > wrote:
> >> Also, just as a reminder for those not familiar with Trac, all
> >> resolutions, no matter their label, close the ticket.
> > I'm under the assumption at this point that, unless we hear otherwise
> > Otto or someone, that the original Trainee Workflow idea isn't feasible.
> > under that assumption, we'd have no need for "suggest-approval" or
> > "suggest-not-approved" as ticket resolutions.
> The problem with the idea of a suggest-whatever resolution and the
> ticket closing has to do with how trac works. When a ticket is closed,
> changing it to another resolution means reopening it and then
> resolving it with the new resolution. Two steps, basically. This
> rapidly becomes annoying.
> Now, the TracWorkflow *is* adjustable, but I don't know much about how
> to do it at present. Here's a page on the topic:
> For those who don't want to read through it all, this graphic
> illustrates the default workflow:
> The wiki page has several examples of how we can modify it to have
> "review" states or similar. We can try to implement some of those if
> it would be helpful to the process.
> theme-reviewers mailing list
> theme-reviewers at lists.wordpress.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the theme-reviewers