Hi, Im looking for a free/open source bug tracking tool that doesn't require a database. Any Recommendations? Thanks in advance.
RWendi
Hi, Im looking for a free/open source bug tracking tool that doesn't require a database. Any Recommendations? Thanks in advance.
RWendi
Given that any bug tracking tool will contain lists of bugs which can be queried in a variety of ways - It's highly unlikely that you can find a tool which does not use some kind of database.
However - You can look for one which uses a database which doesn't need a database engine like MySQL or MSSQL. You need to look for one which uses something like SQLite.
http://en.wikipedia.org/wiki/Comparison_of_issue_tracking_systems
e.g.
- Spiceworks Desktop
- BugWiki
- CVSTrac
- Trac
- Volo Fixer
Alternatively, there's always your spreadsheet or (as with my first bugtracker) pieces of paper that lived in a specific pile on my desk.
You're asking for something that manages a large amount of data but doesn't require a database. Why?
MySQL is free, easy to manage, and can be installed on a linux system with one command if it isn't there already (there's a windows version too).
As a bug tracking tool (that does require a database), Bugzilla is pretty good. The one problem we do have with it is that it doesn't make it easy to track what bugs are in different branches: we often have multiple maintenance branches which different customers use and it can be hard to track what bugs are still in which. Apart from that it works well and not too hard to set up.
I've used Mantis - and there is an Instant Mantis setup that essentially is like Mantis-in-a-box. Worked great
I just want something that's lightweight, simple, easy to install and use... That's the reason why im not looking a system that wants me to install a certain database...
Well anyway, sounds like trac is a very good option, and it has integration to svn too... awesome... thanks guys...
FogBugz and SourceGear Vault integrate very well together and are very easy to set up and use.
Yes, I have a suggestion: maybe you want to search the site before posting questions like this. This particular question has already attained FAQ status and there's an excellent Q & A thread here with lots of good suggestions.
We went with JIRA, and never regretted it, although it has its annoying points. The main feature that sold it for us is the ability to define our own workflow, so we don't adjust our processes to the tool, but we can adjust the tool to our processes (however bad they are ;), as it should be.
It has a standalone version that has a built-in database, since you are so afraid of databases ;)