You commit your issue database to the same repo as your code and track it alongside your code. Then you just need a tool to manage the database for you, and the

You commit your issue database to the same repo as your code and track it alongside your code. Then you just need a tool to manage the database for you, and there's a few tools out there to do this: http://ditz.rubyforge.org/ http://ditz.rubyforge.org/ http://pitz.tplus1.com/ http://pitz.tplus1.com/ https://github.com/jeffWelling/ticgit https://github.com/jeffWelling/ticgit http://www.bugseverywhere.org/ http://www.bugseverywhere.org/ ... and probably others. That's just based on a quick Google search. One nice thing about this approach is that your issue's state follows your code through merges. When you fix the bug you mark it as 'fixed' and commit that change to a branch. When it gets merged into master, the 'fixed' status gets merged as well.