Do you try to do a bug tracker or a "generic" issue tracker/task planner ?
Quick note about bug tracker ? * I like id like JIRA, projectPrefix-projectNum and not a global Num (cross project) * supporting part of the JIRA remote API will simplify integration with third-party tool (hudson, eclipse,...) but need to have specs of the JIRA' remote API * for open-source/public project having a voting system could be usefull (not for internal project) * support wiki syntax for description and comments * support for export/import project * support sub-project * I've got other suggestion (as JIRA admin/users) like permissions/groups management * .... so many feature, so few time => do it simple and good luck Do you want I setup hudson to build and deploy the project on snapshots repo ? /davidB On Sun, Jan 11, 2009 at 09:51, Viktor Klang <[email protected]> wrote: > I've used FogBugz and Mantis, and here are my conclusions for a good > issue-tracker: > > 1) Good integration possibilities (API:s to hook into, different > VCS-backends etc) > 2) Clean and intuitive UI > 3) A priority list is NOT a list with items with different priority > levels!!! > A priority list is a list in prioritized order, so if you move an item > down, you lower it's priority > 4) It HAS TO support unicode characters properly (Yes Mantis, I'm looking at > you) > 5) It has to be able to store and display screenshots easily > 6) It mustn't be a project management tool > 7) It should use an open authentication implementation, so it's not yet > another password to remember > 8) It should be possible to make "templates" for issue-submission > 9) It should be possible to make templates for responding to issues. > 10) Also, I think reporting of statistics should only be done either by > plugins or by external software, and that the issue-tracker can expose it's > raw statistics through API. > > > I hope I didn't forget anything. > > Cheers, > Viktor > > On Sat, Jan 10, 2009 at 1:38 AM, 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 >> >> > > > > -- > Viktor Klang > Senior Systems Analyst > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
