I was thinking to disable the ConfigurableTicketWorkflow and create one that
manages different ticket types.

On Mon, May 11, 2009 at 10:29 PM, John M Camara
<[email protected]>wrote:

>
> At this point in time you can only define one workflow in trac.  I had
> a similar need that you have and worked around the issue by defining
> one very large workflow with the first transition being a selection of
> ticket type.  To make the ticket type selection I changed the New
> Ticket menu item to display a web page that allows the user to select
> a ticket type and then do a HTTP POST to the newticket url with the
> selected ticket type and the status set to the first workflow state
> associated with the sub-workflow of the desired ticket type.
>
> When you make a large workflow like this you also want to use the
> showworkflow script that is available in the repository at trunk/
> contrib/workflow/.  With this script you can generate a graph of the
> workflow to verify the custom workflow configuration is setup as you
> expected.
>
> On May 7, 11:02 am, eri x <[email protected]> wrote:
> > Hi, i want to make a plugin for managing different workflows for
> different
> > ticket types,my idea is to have different workflow section in the
> trac.ini
> > and i was looking into the trac source code to see how does trac knows
> what
> > can do each ticket, i saw now that default_workflow reads only
> > [ticket-workflow] but maybe modifying it i can get trac to sees different
> > worklow section based on ticket type.If these work than i should create a
> > gui plugin for managing the different workflows.
> > Regards Ermal
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Trac 
Development" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/trac-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to