Distributed bug-tracking systems?

[Joshua Judson Rosen]

I switched over to the new-fangled distributed version control,
a couple years ago, and have been utterly delighted.

More recently, I came upon the idea of applying the same technology
to *bug-tracking*; a few systems being:

    Bugs Everywhere <http://bugseverywhere.org/>

    Simple Defects <http://syncwith.us/>

    ditz <http://ditz.rubyforge.org/>

The idea of distributed bug-tracking--being able to go offline
and still be able to file bug-reports and -resolutions without
having to switch over to a different mode of operation
(like `write it down in my notebook and remember transcribe it
 all into the BTS when I'm online again)--sounds pretty awesome.

The idea of bundling the code's bug-state into the DVCS with
the code itself--and not having to manually keep track of
which branch contains which bugs/fixes--also sounds pretty
awesome.

I'm aware, of course, of various theoretical limitations
in the whole idea (doing things like automatically passing
bug-status across merges), but there are lots of things
that are practicable regardless of theoretical issues
(in theory, CVS never should have worked--but, in practice,
it's been used to great success by zillions of developers
for decades).

So, I'm wondering: does anyone here have any experience
doing distrubuted bug-tracking with tools BE, SD, ditz,
or anything similar? How does it work? How do they compare?

-- 
"Don't be afraid to ask (λf.((λx.xx) (λr.f(rr))))."