(I'm the Co-Author)
We announced it on hackernews already some time ago - we are working on a new git-based distributed issue tracking tool.
Version 0.2.0 was released about two weeks ago - go and try it out!
Why do we need another "issue tracker"
Issue tracking in github/gitlab/bitbucket and all these other (fairly cool) platforms and tools is centralized. This means if the service goes offline, your issues are gone. You can continue working on your source, because git is decentralized - but issues belong to the code and so do pull requests (PRs are - in our understanding - a special form of issues).
Of course, there are tools out there already - bugseverywhere, ditz, fossil (which is not an issue tracker but a VCS by itself) and many more. So why do we need another one?
Because we think that these issue trackers did one thing wrong - they did not optimize issue tracking for decentralization.
The new approach
With git-dit, the issue messages are commits without diff. It sounds like a really simple approach - but it gives us super-powers: Having trees as discussions (instead of linear discussion) like on a mailinglist is possible, issues can be merged, transfered between repositories, ... the possibilities are endless!
Of course we want to provide tooling to sync with github/gitlab/... and of course we want to integrate mailing lists - so you can be truly distributed with your issue tracking!
Ask me questions
For more information, head over to the github repository.
We are not yet self hosted, we cannot integrate github issues yet (though the functionality for issue tracking is featurecomplete - there are just no integration tools available yet).
We are also planing a web-interface for the issues, which will be implemented as bachelors thesis at our university by a student we (the main author and I) know.
Feel free to open issues on github or ask questions here - and of course feel free to try it out and report bugs!