seanhussey at gmail
May 7, 2008, 5:40 AM
Post #6 of 10
(139 views)
Permalink
|
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?
Thanks!
Sean
On Tue, May 6, 2008 at 9:03 PM, Richard Liao <richard.liao.i[at]gmail.com> wrote:
>
> blah.set_owner = username
> where username is a specific name. e.g.
> blah.set_owner = hussey
>
>
>
> On Wed, May 7, 2008 at 6:05 AM, Sean Hussey <seanhussey[at]gmail.com> wrote:
> >
> > Which version are you in? I can't seem to get blah.set_owner =
> > username to work. Is username in quotes? Anything special about it?
> >
> >
> >
> > On Fri, May 2, 2008 at 7:44 AM, Christian Unger <christian.unger[at]mac.com> wrote:
> > >
> > > ok I found the solution to my first question:
> > >
> > >
> > > deploy = fixed -> deployed
> > > deploy.operations = set_resolution, set_owner
> > > deploy.set_owner = username
> > > deploy.permissions = TICKET_MODIFY
> > >
> > >
> > > now on to my 2nd, anyone?
> > > :-)
> > >
> > >
> > > cu
> > > christian unger
> > >
> > >
> > >
> > >
> > >
> > >
> > > On 02.05.2008, at 11:29, cunger wrote:
> > >
> > > >
> > > >
> > > > Hi,
> > > >
> > > > while I am currently playing around with the Configurable Ticket
> > > > Workflow in trac 0.11, two questions came to my mind and I do not seem
> > > > to find a documented solution to them.
> > > >
> > > >
> > > > 1 - Is it possible to assign default values to specific stages of a
> > > > workflow?
> > > >
> > > > the idea is to define one person who is always responsible for the
> > > > processing of the report in a specific stage,
> > > > say you have committed your fix into the repository and mark the
> > > > report as fixed.
> > > > the fact that the report's soultion is set to fixed should propagate
> > > > it's status to say 'deployed' and set the owner of the report to the
> > > > person responsible for deploying the next version of the product to
> > > > QA.
> > > >
> > > > The section of the workflow would look somewhat like this:
> > > >
> > > > deploy = fixed -> deployed
> > > > deploy.operations = set_resolution, set_owner_to_('Username')
> > > > deploy.permissions = TICKET_MODIFY
> > > >
> > > > Is this possible?
> > > >
> > > >
> > > >
> > > > 2 - Make specific ticket properties inaccessible for reporters
> > > > upon ticket creation the reporter schould only be able to set the
> > > > values of a subset of the available fields.
> > > >
> > > > How do I configure this?
> > > >
> > > >
> > > > cu
> > > > christian unger
> > > >
> > > >
> > > > >
> > >
> > >
> > > >
> > >
> >
> > >
> >
>
> >
>
--~--~---------~--~----~------------~-------~--~----~
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[at]googlegroups.com
To unsubscribe from this group, send email to trac-users-unsubscribe[at]googlegroups.com
For more options, visit this group at http://groups.google.com/group/trac-users?hl=en
-~----------~----~----~----~------~----~------~--~---
|
