Ok, this is bizarre. I copied the db, trac.ini and plugins from the bugged instance to the new one, so the instances were pretty much the same. Well, not "pretty much", they *are* the same as far as I know. And the problem with the ticket type being reset to "Bug" only happens in the old instance, *not* in the new one. So I just swapped the two instances and now I can go on my merry way. That's a mystery I probably never will resolve.
-- Sébastien. 2010/6/17 Sébastien Volle <[email protected]> > Thank you for your reply Robert. I did some clean up in my trac.ini and the > plugins directory. I also updated to Trac 0.11.7-3. Maybe this will help on > the burndown issue. > > I still have the problem with the ticket type that doesn't "stick" when > editing a ticket though. I tried on a new instance and I don't have the > problem. I suspected something was off in our production DB so I copied it > to the new instance but the problem still didn't show up. I fiddled for a > time with trac.ini, disabling components, resetting workflow to default etc, > but to no avail. > I'm using the same codebase for both instances, the db is the same and the > configuration is virtually the same as well and yet, only one instance has > the bug. > > I am officially stumped :) > > Regards, > Sébastien > > > 2010/6/17 Robert Buchholz <[email protected]> > > Hi Sébastien, >> >> >> On Thursday 17 June 2010, Sébastien Volle wrote: >> > You should note that the Trac instance we're using is pretty old, ie >> > it has undergone a lots of customization but this I don't see how it >> > could affect how the burndown chart is generated. >> >> While you're not using the most recent 0.11.x release, your version is >> not known to cause this amount of headache. In 1.3.0.1, the burndown >> history (i.e. remaining time before now()) is stored in the database, >> and not calculated on the fly. So in theory, if you see a burndown data >> point at 42 two days ago, it should still be there tomorrow. In previous >> versions, if tickets changed their type or lost some fields, they would >> be lost for historic burndown calculation. >> >> The exact issue that you described is not something I have heard before. >> I would strongly encourage you to try Agilo on a vanilla trac instance >> and re-add the plugins you have installed as needed. It's probably an >> interaction between Agilo and one of them that causes the issue, but I >> cannot say which one it would be -- maybe the timingandestimationplugin? >> >> >> Regards >> >> Robert >> >> -- >> 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] <agilo%[email protected]> >> For more options, visit this group at >> http://groups.google.com/group/agilo >> > > -- 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
