My bug tracking wishlist: 1) Pluggable integration with source control systems so that fixed bugs can easily be associated with the relevant patch sets in the vcs.. The rise of distributed version control systems like Git has had me thinking about the possibility of providing a patch as a link or list of changesets to pull from instead of a text file that may or may not apply cleanly to the current version of the trunk. Being able to rebase someone else's patchset against the current trunk could be incredibly useful.
2) Mailing list integration. It's not uncommon for bug trackers to post new bugs to relevant addresses or mailing lists, but I've never seen one where the bug tracker itself can filter out and record the resulting thread from the list; often the on-list discussion is pretty valuable to the resolution. 3) Most bug trackers that I've seen have utterly crap ways of prioritizing bugs (a scale from 1-5 is useless) or relating bugs/feature requests to one another. Often when I'm working on a project, I'll organize my non-critical bugfixes so that they are handled when I touch the relevant sections of code for other purposes; if I'm planning to add a feature somewhere in my app, it's not uncommon that in the process of refactoring that section existing bugs get taken care of as part of the process. In terms of prioritization, I'd love a system that gives my manager/users a clear idea of when a particular bug will be fixed, and perhaps why it's behind a bunch of other, more pressing issues. People love it when they can see their issues trickling towards the head of the queue. Kris On Fri, Jan 9, 2009 at 5:38 PM, David Pollak <[email protected]>wrote: > Folks, > > I'm please to announce my latest open source project: Swampland. > http://github.com/dpp/swampland/tree/master > > Swampland is a bug/issue tracking system built on Lift. It's licensed > under the GNU Affero General Public License (there will be a classpath > exception so Swampland can be run in non-free web containers). > > I'm going to be working on Swampland over the next bunch of weeks and it > will form the basis for the Lift project's bug tracking system. It will > also likely be the project the I use in the Lift book. > > Early in the process, I'd love to hear from folks about the good and bad of > various bug tracking system they use so I can use the good and avoid > pitfalls. > > My key goal for Swampland is to build something that's got a very usable > UI, but also has a RESTful interface that's a first-class part of the > system. It will support plugins. > > I'm licensing it under a GPL license because I want to make sure that > anyone who uses it and updates it contributes code back to the project. > > Thanks, > > David > > -- > Lift, the simply functional web framework http://liftweb.net > Collaborative Task Management http://much4.us > Follow me: http://twitter.com/dpp > Git some: http://github.com/dpp > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Lift" group. 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/liftweb?hl=en -~----------~----~----~----~------~----~------~--~---
