bugzy - command line bug/issue tracker

Maintains issues/bugs/enhancements/features for projects using an sqlite3 database. Developed on ruby 1.9.1.

This is a simple, command-line bug tracker for small projects. This is not web-based and does not integrate with git or any other system. It is not meant for large, distributed, multi-user projects.

You may either use a bug database per project, keeping it in the folder of the project. You may also keep one global database for various projects.

This depends on the following gems: sqlite3-ruby, arrayfields, highline, subcommand (a tiny wrapper over optparse) and optionally on terminal-table (if you want tabular output). You may also get bare, delimited output to use for filtering.

Links

Installation

sudo gem install bugzyrb

Purpose, or why another bug tracker

I had problems installing various bug-trackers on my system (Mac OSX). I downloaded some ruby ones, and one was dependent on broken gems. Even after fixing it, it was excruciatingly slow -- I think it used activerecord. Another one does not work on 1.9.1 and the fork that fixes that crashes out with other errors. So after a lot of time, trying installing, running, forking, I wrote a simple bug-tracker using bash (bugzy.txt) using a tab delimited text file.

I now want to port that to ruby (and sql) so I don't have to fight the incompatibilities between BSD, GNU commands such as -- well all of them -- but date was quite a meanie. This is not a feature-rich, integrated system like bugzilla, or any other. It's just a simple system storing:

I may add version, project, component at some stage.

Ideally, a person would create one sql database in each project. However, if one wishes to have one repo for multiple projects, a project field can be added. Currently, the title can contain a project tag, or version tag, to keep it simple.

Emails are sent at bug creation, and update.

There is no web or server involved, or integration with git etc. Suggestions are welcome.

I'd like to keepit small and simple, so others can easily modify it for their own needs: adding fields or removing should be easy.

Sample output (trimmed)

 TODO