The idea behind Ditz is that, if your project has no centralized "truth", then a bug tracker that represents centralized "truth" doesn't make much sense. Instead, Ditz keeps track of your bugs right there in your Git repo, so when you check out that 3 month old experimental branch, all of the bugs that still existed on it are right there for you to read about.
Comments
As I read this I immediately thought of Ditz (http://ditz.rubyforge.org/).
The idea behind Ditz is that, if your project has no centralized "truth", then a bug tracker that represents centralized "truth" doesn't make much sense. Instead, Ditz keeps track of your bugs right there in your Git repo, so when you check out that 3 month old experimental branch, all of the bugs that still existed on it are right there for you to read about.