If you really want to save time, building a bug tracker is not the way to do it.
But if you want to build one as an exercise, it's probably not a bad idea. It's hard to say how valuable the integration points would be. I'm usually pretty skeptical of stuff like that. There are probably ways to get Web2py tickets automatically inserted into bug trackers. On Thursday, May 31, 2012 7:25:36 AM UTC-7, encompass wrote: > > I have noticed one other tracker in web2py, but I couldn't demo it. > Besides that it is cloning, and I wonder if I could just start from > scratch with a few features. > One in particular is integrating with web2py a bit. > For example, seeing tickets for a particular app and binding the ticket > to a new bug. Or integration with Hg to close bugs with commits. > The reason I want to build one in web2py is because I don't want to have > to setup a special environment just for my tracker. I want to use > similar deployment recipes to save time. The bonuses could be the > integration into web2py and hg. > Other things that might be nice is integration with reported issues from > customers/users. It would provide a bug reporting interface that is > access from clicking on the ticket when not connected locally accessing > it. > BR, > Jason > >
