Distributed bug tracking

Although I'm still not convinced from DVCS, the idea to have the bugs in 
the same directory tree as the project sounds like a really good idea to 
me.
I mean, with regular bugtrackers like mantis, bugzilla, Trac you have to 
dig through a big database of bugs by using the right search fields.

It would be so much more productive if I could just do something like

CMake/Modules/$ ls
.....
FindQt4.cmake
... more files

# now ask for bugs:
CMake/Modules/$ buggy list FindQt4.cmake
   #1234 "It doesn't work"
   #1345 "Sometimes it fails"
   #3454 "If I do something wrong, it fails" 
CMake/Modules/$ buggy show 1234
   Title: It doesn't work
   Reporter: Karl Karlsen
   Note: If Qt4 isn't installed, FindQt4.cmake doesn't find it !
CMake/Modules/$ buggy change 1234 nochangerequired
CMake/Modules/ $ cd ..
CMake/ $ buggy list
   #1 General: "CMake works too good"
   #2 
   ...
   #1345 FindQt4.cmake: "Sometimes it fails"
   ...

Also for a huge project like KDE this would be a huge gain I could 
imagine.

I also have the suspicion that this will need really tight integration 
with the VCS (which I think doesn't necessarily have to be a DVCS).

A comment about DVCS: now honestly, is "committing to a local repository" 
really worth that much ? I mean, it is still on my local harddisk. So it 
is not backed up as on a central server. Still nobody else can see the 
code, so there is no peer review yet. Still nobody else can test the 
code. Doesn't this encourage big commits later on to the official/main 
tree, which are too big to understand easily ?
I completely agree that having version control also for local files is a 
vey nice thing, but IMO this is different from using a VCS for 
development.

Alex