I need something that's open source (or very cheap) that I can use at home. I do side work and cannot afford something like ClearQuest.
I would really like to run this tool from my dev machine without using a server.
I need something that's open source (or very cheap) that I can use at home. I do side work and cannot afford something like ClearQuest.
I would really like to run this tool from my dev machine without using a server.
Here are three:
EDIT: When you say you don't want a server, do you mean you don't want a remote server, or do you mean you don't want to set up a Web server on your local machine?
I use BugTracker.NET, very simple and convenient, but it's ASP.NET, if you don't want install it on server, you can install on your localhost.
For a one person team I'd use a word-processor or a spreadsheet. But then, I'd use a word processor or a spreadsheet for a 5 person team too so long as they are all in the same room or not too far away from each other. Whaddya wanna do, spend time installing and feeding Bugzilla (or one of the other fine systems proposed) or developing and scribbling down a few notes on bugs now and then ?
I like Redmine very much. It has several features that Trac hasn't, most notably support for sub-projects. The Wiki is sucky but it can be replaced. It runs on Ruby on Rails. Bitnami has ready-made installation packages, also for Windows as an installer or even as a lightweight Linux-based virtual machine.
why don't u use just a simple excelsheet? especially if you are just one person and as i have read from your post, nobody else need some access to it..
I'd recommend FogBugz because it's a good commercial tool that is free for startups, i.e. up-to 2 people. Plus it's managed so there's nothing to set-up.
I've been using it for 3 years now and have no complaints.
High Performance Mark's suggestion to use a spreadsheet/word processor isn't that bad of an idea. If the project is small and involves just several people, it can be a hassle to install a web server, configure it, and then configure and maintain a dedicated bug tracking package, especially if you're strapped for time or don't want to experiment.
Sleske remarked that updates can be a problem. That is true, but only if you opt for a file in a shared folder. To get around this, you could trying Google Documents, which handles concurrent access and version control very well. Fields that are being updated by another user are locked, and if something goes wrong, there's always revert.
Sure, a decent bug tracking solution has way more features and is vastly better in terms of usability, but if you want something simple for no more than a couple of developers, Google Docs might be an okay choice.
I prefer Artifacts for my personal Visual Studio projects, because it is very simple and lightweight bugtracker. If you don't want spend time to server installation it should be your solution. Good luck!