Distributed Bugtrackers

The idea is basically that if you use DVCS, you keep your bug database in the repository, and move it around like the rest of your code. It means you don't need a separate store for your bugs, you can record a fix along with committing the fix, you can see the state of the bug database and corresponding codebase at any point in time, and the database can be used offline. It also means that QA will need commit access to the repository, checkouts of old revisions won't include any mention of bugs they contain which were only reported later, comments on bugs don't propagate any faster than code, and will be lost in closed branches, and there's no idea of a canonical single bug state (although if you have a golden master repository somewhere, there sort of is). Anyway, interesting idea.

• Bugs Everywhere - works with Mercurial, Git, and many, many more; bugs are at least similar to maildir. Too many commands to list (not that many, just lazy), has predefined metadata for issues, has email and web interfaces and so on. Pretty sweet?
• b - Mercurial extension; bugs are flat text. Commands are add, rename, (list) users (and bugs assigned to them), assign, details, edit, comment, resolve, reopen, list (filter by owner, title), id (expand ID prefix to full ID), version (of b).
• Artemis - Mercurial extension; bugs and comments are maildirs with arbitrary properties in mail headers. Commands are iadd (issue or comment, can add attachments; also updates properties on existing items), ilist (can filter by properties or predefined property filters), ishow. Fewer commands than b, but almost everything b can do, Artemis can do with properties (can't get bug count alongside user list, can't expand ID prefix) - aliases could make it easier.
• Pitz - standalone (doesn't interact with DVCS?), works inside your repository; bugs are some sort of YAML file or something. Seems like more of a framework for issue tracking than an issue tracker itself. Incredibly flexible. Maybe a bit too flexible. UI for creating stuff is a Python REPL.
• TicGit(-ng) - standalone, but uses Git (standalongside?). Keeps issues on a separate branch to code, which is interesting - i think this could be a general technique for some kinds of metadata.
• Fossil - is a DVCS! Started a few years after Git and Mercurial, it's like them, but with built-in issue tracking, wiki, web server, and all sorts.
• Mercurial Bugtracker extension - Mercurial extension. Commands are add, close, open, modify, show, bugs.