One man bugtracker?
FogBugz has a student/startup edition that’s free indefinitely, for 2 or less users.
FogBugz has a student/startup edition that’s free indefinitely, for 2 or less users.
Issue tracking systems usually integrate more with customers and customer issues. An issue could be “help me install this” or “How do I get the fubar into the flim flam.” They could even be something like “I need an evalutation key for your software”. Bug tracking systems help you keep track of wrong or missing … Read more
Edit: Bugzilla 6.0 will include optional markdown support; it was implemented as a GSoC project in the bug linked in the question. Docs. Before 6.0, the only thing it supports is the > prefix on lines, which makes them purple and not wrap.
You should take a look at Redmine (http://www.redmine.org/). It has all of the features you mention and more. You can host it on your own vps (I do).
Verify the steps used to produce the error Oftentimes the people reporting the error, or the people reproducing the error, will do something wrong and not end up in the same state, even if they think they are. Try to walk it through with the reporting party. I’ve had a user INSIST that the admin … Read more
First, look at these Ohloh metrics: Trac: 44 KLoC, 10 Person Years, $577,003 Bugzilla: 54 KLoC, 13 Person Years, $714,437 Redmine: 171 KLoC, 44 Person Years, $2,400,723 Mantis: 182 KLoC, 47 Person Years, $2,562,978 What do we learn from these numbers? We learn that building Yet Another Bug Tracker is a great way to waste … Read more
I think you’ll find that your team will like either Trac or Redmine more than Bugzilla or Mantis. Both integrate nicely with Subversion. Both include wiki, forums, project management features… Quick overview: Trac: Very widely used and loved, written in python, huge community, lots of “plugins”. A common complaint is that it doesn’t support multiple … Read more
Bitbucket already supports marking issues on commit using the Issues service. The issues service scans commit messages for commands which will automatically change the state of the relevant issue on the tracker. [snip] Examples: “… fixes #4711 …” # marks issue as resolved “… reopening bug 4711…” # marks issue as open “… refs ticket … Read more
Google is calling it Chromium on Google Code The Chromium Bug Reporting Page is there and has the link to submit bugs listed. (Google Account Required) Here’s a direct link to the bug report form.