Thanks for the response.  We figured out what was causing the
problem.  We had created a new ticket type called 'Business Rule' that
can be linked to Requirements.  The 'requirement.business rule.copy'
line in trac.ini included the field 'type'.  Since type was already in
the arguments list on this line of code in agilo_links_edit.html:

<li><a href="${href.newticket(type=item.dest_type,
src=ticket.id, **copied_fields)}">Create a new referenced '$
{ticket.get_alias(item.dest_type)}'</a></li>

Python apparently didn't like it being referenced by **copied_fields
as well.

I edited trac.ini to remove the 'type' field from all of the
'*.*.copy' lines and that fixed things.  I'm not sure why 'type' was
there in the first place--I don't think we put it there explicitly
when creating the new ticket type.

Thanks,
Tom

On Nov 2, 4:51 pm, Andrea Tomasini <[email protected]>
wrote:
> On Mon, Nov 2, 2009 at 10:34 PM, TomHerrick <[email protected]> wrote:
> > I work with Craig and have been trying to troubleshoot this issue.  We
> > aren't able to upgrade our trac/agilo instance right now (currently
> > running 0.11.5 and 1.0.1-PRO respectively), but I did download the
> > latest version and loaded it on another system to see if it would
> > resolve our problem.  When I imported our database, the same error
> > message still occurred on the 1.1.0-PRO version.
>
> > Any other suggestions?  We get this error any time we try to edit a
> > 'requirement' type ticket, so this is a real show-stopper for us.  It
> > doesn't affect other ticket types, though.
>
> It might have something to do with the link structure, the error seems
> to infer that one of the linking type is actually propagated with more
> than one value... that means you might have the situation of a double
> link type from or to requirement? Can you check that, or paste here
> your trac.ini [agilo-links] section?
>
> I see a point in the code where this might generate a problem... there
> is an assumption that the value is unique... might be a list and would
> be correct... if so, can you check if that is the case?
>
> > Thanks,
>
> Thank you
>
> > Tom
>
> ANdreaT

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