Hi all,

After investigating, I've discovered the cause of my original problem:

Agilo is setting the 'type' attribute of the 'ticket' object (excuse
me if I'm using the wrong terminology since I'm not familiar with
Python) to the string that is defined as the alias of the type. For
example, we have aliased the "bug" ticket type so that (in many
places) it gets shown as "Defect". When you look at the 'type'
attribute with Agilo running, "bug" is not returned, but "Defect" is.

Since our workflow specification was filtering on <action>.ticketype =
bug, there was no match, and the functionality broke.

We have worked around this problem by changing our specification to
use the alias name.

So, from our experience so far, Agilo can be made to work with the
TypedTicketWorkflow plugin using the above workaround.

Thanks.

On Nov 30, 5:20 am, [email protected] wrote:
> Hi guys
>
> We've using ConfigurableTicketWorkflow in Agilo at the moment. How did you 
> deploy the plug in?
>
> Iain
> Sent from my BlackBerry® wireless device
>
> -----Original Message-----
> From: Garbrand van der Molen <[email protected]>
> Date: Mon, 30 Nov 2009 10:12:32
> To: <[email protected]>
> Subject: Re: [Agilo for Scrum] TypedTicketWorkflow compatibility problems,
>
>         anyone?
>
> Hi,
>
> As far as I know neither ConfigurableTicketWorkflow nor  
> TypedTicketWorkflowPlugin work with agilo at the moment.
>
> Regards,
> Garbrand
>
> On Nov 27, 2009, at 17:40, tcchau wrote:
>
> > Hi all,
>
> > We attempting to use Agilo for Scrum with our Trac installation. I've
> > found that it is incompatible with the TypedTicketWorkflowPlugin
> > (http://trac-hacks.org/wiki/TypedTicketWorkflowPlugin). We use this
> > plugin so that we can enforce different workflows depending on the
> > type of ticket that is under consideration.
>
> > When enabled, certain state transitions or actions are not available.
>
> > Has anyone else ever come across this problem? I'd like to poll the
> > community to see if there are any obvious workarounds before I delve
> > into the code to figure it out myself.
>
> > Thanks.
>
> > --
> > Follow Agilo on Twitter:http://twitter.com/agiloforscrum
> > -----
> > You received this message because you are subscribed to the Google
> > Groups "Agilo for Scrum" group. This group is moderated by agile42  
> > GmbH
> >http://www.agile42.comand is focused in supporting Agilo for Scrum  
> > users.
> > 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/agilo?hl=en

-- 
Follow Agilo on Twitter: http://twitter.com/agiloforscrum
-----
You received this message because you are subscribed to the Google
Groups "Agilo for Scrum" group. This group is moderated by agile42 GmbH 
http://www.agile42.com and is focused in supporting Agilo for Scrum users.
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/agilo?hl=en

Reply via email to