Mailing List Archive: Trac: Users

Having Specific Workflows for Each Ticket Type

Index | Next | Previous | View Threaded

chris at reemergemedia

May 6, 2008, 2:45 PM

Post #1 of 6 (79 views)
Permalink

Having Specific Workflows for Each Ticket Type

Is it possible to define a particular workflow for Tasks and have a
different workflow for Defects? Would Trac take nicely to changing the
trac-workflow in mid-stream development? For example, the default
workflow is great for straight tasking, but when a defect gets entered
into the system we'd like to have it go through a Q/A process. So in
that instance the enterprise workflow sample would be desired.

I found this in the Trac wiki but am not sure if it exactly addresses
it (had a hard time following it).

"A workflow plugin can add an arbitrary workflow operation, so this is
already possible.

set_actor should be an operation allowing to set the owner, e.g. as a
"preop":
either to a role, a person
entered fix at define time, or at run time, e.g. out of a field, or
select.
This is either duplicating the existing set_owner operation, or needs
to be clarified.

Actions should be selectable based on the ticket type (different
Workflows for different tickets)

This is becoming a frequent request, with clear usecases. The closest
the current implementation will allow is to have a plugin provide a
triage action that sets the next state based on the ticket type, so a
new ticket would move to new_task, new_defect, etc., and the workflow
graph would separate at that point."

Thanks.
Chris
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

kantrn at rpi

May 6, 2008, 3:21 PM

Post #2 of 6 (76 views)
Permalink

Re: Having Specific Workflows for Each Ticket Type [In reply to]

On May 6, 2008, at 5:45 PM, Chris wrote:
>
> Is it possible to define a particular workflow for Tasks and have a
> different workflow for Defects? Would Trac take nicely to changing the
> trac-workflow in mid-stream development? For example, the default
> workflow is great for straight tasking, but when a defect gets entered
> into the system we'd like to have it go through a Q/A process. So in
> that instance the enterprise workflow sample would be desired.
>
> I found this in the Trac wiki but am not sure if it exactly addresses
> it (had a hard time following it).
>
> "A workflow plugin can add an arbitrary workflow operation, so this is
> already possible.

There seems to be some confusion between the core workflow system
(ITicketActionControler) and the include ConfigurableTicketWorkflow.
The trac.ini-based system is designed to allow for simple
configuration, but doesn't come close to allowing the full flexibility
of the underlying framework. Personally I think this is fine, people
are just very averse to learning Python just to be able to implement
their workflows. This is also understandable, but I would rather see
the community step up and provide workflow plugins for other common,
but not simple enough to be in ConfigurableTicketWorkflow, use cases.

--Noah

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

retracile at gmail

May 6, 2008, 8:03 PM

Post #3 of 6 (76 views)
Permalink

Re: Having Specific Workflows for Each Ticket Type [In reply to]

On Tuesday 06 May 2008 05:21:27 pm Noah Kantrowitz wrote:
> On May 6, 2008, at 5:45 PM, Chris wrote:
> > Is it possible to define a particular workflow for Tasks and have a
> > different workflow for Defects? Would Trac take nicely to changing the
> > trac-workflow in mid-stream development? For example, the default
> > workflow is great for straight tasking, but when a defect gets entered
> > into the system we'd like to have it go through a Q/A process. So in
> > that instance the enterprise workflow sample would be desired.
> >
> > I found this in the Trac wiki but am not sure if it exactly addresses
> > it (had a hard time following it).
> >
> > "A workflow plugin can add an arbitrary workflow operation, so this is
> > already possible.
>
> There seems to be some confusion between the core workflow system
> (ITicketActionControler) and the include ConfigurableTicketWorkflow.
> The trac.ini-based system is designed to allow for simple
> configuration, but doesn't come close to allowing the full flexibility
> of the underlying framework. Personally I think this is fine, people
> are just very averse to learning Python just to be able to implement
> their workflows. This is also understandable, but I would rather see
> the community step up and provide workflow plugins for other common,
> but not simple enough to be in ConfigurableTicketWorkflow, use cases.

And I'll chime in and second this. That said, I've created a plugin on
trac-hacks to be something of a common playground for workflow operations:
http://trac-hacks.org/wiki/AdvancedTicketWorkflowPlugin

Also, look at the example CodeReview.py plugin in the Trac source for ideas of
a way to implement a triage plugin.

HTH,

Eli
------------------. "If it ain't broke now,
Eli Carter \ it will be soon." -- crypto-gram
retracile[at]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[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
-~----------~----~----~----~------~----~------~--~---

chris at reemergemedia

May 7, 2008, 12:24 PM

Post #4 of 6 (69 views)
Permalink

Re: Having Specific Workflows for Each Ticket Type [In reply to]

Noah,

So you're saying it's possible to create a plug-in that could assign a
particular workflow based on the ticket type? And that this would have
to be a plug-in as it's too complex for the ticket-workflow in
the .ini? I can visually see how this would work in the admin
interface, actually pretty slick, but as for implementing it
myself.... heh. Looks like my spare time is going to be devoted to
learning Python. :)

Chris

On May 6, 6:21�pm, Noah Kantrowitz <kan...@rpi.edu> wrote:
> On May 6, 2008, at 5:45 PM, Chris wrote:
>
>
>
> > Is it possible to define a particular workflow for Tasks and have a
> > different workflow for Defects? Would Trac take nicely to changing the
> > trac-workflow in mid-stream development? For example, the default
> > workflow is great for straight tasking, but when a defect gets entered
> > into the system we'd like to have it go through a Q/A process. So in
> > that instance the enterprise workflow sample would be desired.
>
> > I found this in the Trac wiki but am not sure if it exactly addresses
> > it (had a hard time following it).
>
> > "A workflow plugin can add an arbitrary workflow operation, so this is
> > already possible.
>
> There seems to be some confusion between the core workflow system �
> (ITicketActionControler) and the include ConfigurableTicketWorkflow. �
> The trac.ini-based system is designed to allow for simple �
> configuration, but doesn't come close to allowing the full flexibility �
> of the underlying framework. Personally I think this is fine, people �
> are just very averse to learning Python just to be able to implement �
> their workflows. This is also understandable, but I would rather see �
> the community step up and provide workflow plugins for other common, �
> but not simple enough to be in ConfigurableTicketWorkflow, use cases.
>
> --Noah
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

andrei2102 at gmail

May 8, 2008, 11:48 PM

Post #5 of 6 (55 views)
Permalink

Re: Having Specific Workflows for Each Ticket Type [In reply to]

Hi guys,
I created a workflow controller that knows to hide/to show actions based on
ticket fields values, beside other new operations. You can find it at
http://code.optaros.com/trac/oforge/browser/trunk/plugins/workflowcontrollerplugin

All the new functionality can be configured from the trac.ini file. For more
details feel free to contact me.

On Wed, May 7, 2008 at 10:24 PM, Chris <chris[at]reemergemedia.com> wrote:

>
> Noah,
>
> So you're saying it's possible to create a plug-in that could assign a
> particular workflow based on the ticket type? And that this would have
> to be a plug-in as it's too complex for the ticket-workflow in
> the .ini? I can visually see how this would work in the admin
> interface, actually pretty slick, but as for implementing it
> myself.... heh. Looks like my spare time is going to be devoted to
> learning Python. :)
>
> Chris
>
>
> On May 6, 6:21 pm, Noah Kantrowitz <kan...@rpi.edu> wrote:
> > On May 6, 2008, at 5:45 PM, Chris wrote:
> >
> >
> >
> > > Is it possible to define a particular workflow for Tasks and have a
> > > different workflow for Defects? Would Trac take nicely to changing the
> > > trac-workflow in mid-stream development? For example, the default
> > > workflow is great for straight tasking, but when a defect gets entered
> > > into the system we'd like to have it go through a Q/A process. So in
> > > that instance the enterprise workflow sample would be desired.
> >
> > > I found this in the Trac wiki but am not sure if it exactly addresses
> > > it (had a hard time following it).
> >
> > > "A workflow plugin can add an arbitrary workflow operation, so this is
> > > already possible.
> >
> > There seems to be some confusion between the core workflow system
> > (ITicketActionControler) and the include ConfigurableTicketWorkflow.
> > The trac.ini-based system is designed to allow for simple
> > configuration, but doesn't come close to allowing the full flexibility
> > of the underlying framework. Personally I think this is fine, people
> > are just very averse to learning Python just to be able to implement
> > their workflows. This is also understandable, but I would rather see
> > the community step up and provide workflow plugins for other common,
> > but not simple enough to be in ConfigurableTicketWorkflow, use cases.
> >
> > --Noah
> >
>

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

retracile at gmail

May 9, 2008, 6:50 PM

Post #6 of 6 (44 views)
Permalink

Re: Having Specific Workflows for Each Ticket Type [In reply to]

On Wednesday 07 May 2008 02:24:00 pm Chris wrote:
> Noah,
>
> So you're saying it's possible to create a plug-in that could assign a
> particular workflow based on the ticket type? And that this would have
> to be a plug-in as it's too complex for the ticket-workflow in
> the .ini? I can visually see how this would work in the admin
> interface, actually pretty slick, but as for implementing it
> myself.... heh. Looks like my spare time is going to be devoted to
> learning Python. :)

http://trac-hacks.org/wiki/AdvancedTicketWorkflowPlugin

Now (as of a few minutes ago) supports a triage operation.

It lets you create an action that splits the workflow graph based on the value
of a ticket field, such as 'type'. It isn't /quite/ what many want in terms
of different workflows for different ticket types, but it will get you most
of the way there with minimal effort.

Example:
triage = new -> *
triage.operations = triage
triage.triage_field = type
triage.traige_split = defect->new_defect, task->new_task,
enhancement->new_enhancement

Feedback welcome.

Eli
------------------. "If it ain't broke now,
Eli Carter \ it will be soon." -- crypto-gram
retracile[at]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[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
-~----------~----~----~----~------~----~------~--~---

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact lists@gossamer-threads.com