On Tuesday, June 29, 2010, Robert Buchholz wrote: > Hey Stephan, > > On Monday 28 June 2010, Stephan Richter wrote: > > I have just upgraded to Agilo 1.3.0.3 and Trac Import stopped > > working. > > Which version were you on when this worked? I'm not using the Import > plugin, but it is not unexpected that two plugins that both have their > own custom Ticket subclasses is going to break.
I think we were using Agilo 1.2.1 before we upgraded. It worked then, I think, because the burndown chart did not try to detect changes. It was listed as a feature for 1.3.0 as far as I remember. We are using TracImport 0.7c. I agree with you that breakage would be expected. That said, TracImport is pretty vital, I think, to make Trac usable. I and another PM here can simply not deal with all the clicking when trying to create larger amounts of tasks. Regards, Stephan -- Entrepreneur and Software Geek Google me. "Zope Stephan Richter" -- Follow Agilo on Twitter: http://twitter.com/agiloforscrum Please support us by reviewing and voting on: http://userstories.com/products/8-agilo-for-scrum http://ohloh.net/p/agilo-scrum http://freshmeat.net/projects/agiloforscrum You have received this message because you are subscribed to the "Agilo for Scrum" Google Group. This group is focused on supporting Agilo for Scrum users and is moderated by agile42 GmbH <http://www.agile42.com>. To post to this group, send email to [email protected] To unsubscribe from this group, send an email to [email protected] For more options, visit this group at http://groups.google.com/group/agilo
