[prev in list] [next in list] [prev in thread] [next in thread]
List: trac
Subject: [Trac] Re: [0.11] Ticket - Workflow
From: "Sean Hussey" <seanhussey () gmail ! com>
Date: 2008-05-07 13:31:34
Message-ID: c89c8a510805070631v6ab394f2m732673f5aae643b7 () mail ! gmail ! com
[Download RAW message or body]
Ahh, I see. Thank you! I understand it now.
Sean
On Wed, May 7, 2008 at 9:03 AM, Eli <retracile@gmail.com> wrote:
>
> On Wednesday 07 May 2008 07:40:10 am Sean Hussey wrote:
> > Yeah, that's not working for me, but maybe I jumped ahead a few steps
> > in the conversation. I added this to the standard workflow that comes
> > with 0.11rc1 by default:
> >
> > testing = new,accepted,needs_work,reopened -> testing
> > testing.name = Submit to QA for testing
> > testing.set_owner = hussey
> > testing.permissions = TICKET_MODIFY
> > reject = testing -> needs_work
> > reject.name = Failed testing, return to developer
> > pass = testing -> closed
> > pass.name = Passes Testing
> > pass.operations = set_resolution
> > pass.set_resolution = fixed
> >
> > This doesn't handle everything, but the set_owner piece is what I'm
> > most interested in. The username in question is a valid user and is
> > in the session table. We have restrict_owner set to true. The
> > username shows up in that dropdown when we're assigning tickets.
> >
> > Anything else I should look at?
>
> testing.operations = set_owner
>
>
> Eli
> ------------------. "If it ain't broke now,
> Eli Carter \ it will be soon." -- crypto-gram
> retracile@gmail.com `-------------------------------------------------
>
> >
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Trac Users" group.
To post to this group, send email to trac-users@googlegroups.com
To unsubscribe from this group, send email to trac-users-unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/trac-users?hl=en
-~----------~----~----~----~------~----~------~--~---
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic