Hi Stefan, > 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.
For that problem we originally intended the CSV-Export and import of Backlogs which should give you that same functionality from within agilo. For documentation on that, see <https://dev.agile42.com/agilo-help/user/dashboard#ManagingticketsviaCSVfiles>. For the new backlog you need to append ?format=csv to get it. (More details about that in the release notes <http://www.agile42.com/cms/blog/2010/05/27/new-agilo-release-13/>). Regards, Martin -- 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
