When comparing Fossil vs git-bug, the Slant community recommends Fossil for most people. In the question“What are the best self-hosted bug trackers?” Fossil is ranked 3rd while git-bug is ranked 15th. The most important reason people chose Fossil is:
Fossil includes source code management, bug tracking, a wiki, and technotes. It even includes its own web server, though it can fairly easily be incorporated into other webservers.
Specs
Ranked in these QuestionsQuestion Ranking
Pros
Pro Very complete
Fossil includes source code management, bug tracking, a wiki, and technotes.
It even includes its own web server, though it can fairly easily be incorporated into other webservers.
Pro Self-contained
A Fossil repository is contained in a single file.
Pro Cross-platform
Fossil can run on Linux, Mac, BSD derivatives and on Windows.
Pro Very easy to configure as self-hosted
Single, stand-alone executable, including web server.
Pro Needs very few server resources
Since Fossil is a distributed VCS on top of being a bug tracker, it needs very few server resources.
Pro Free
Pro Bridges
git-bug has bridges with other bug-trackers, like GitHub, GitLab and Jira. Use it as your personal local remote interface. Sync with git bug bridge pull and git bug bridge push, work from your terminal or integrate it into your editor.
Pro Online / offline
Can be used online or offline.
Cons
Con Only a web interface or CLI
Fossil's bug tracker only works with the web interface or the command-line interface. There's no native GUI client supporting it.
There are some independent GUI clients out there, but none of them support Fossil's full range of abilities.
Con Web UI beta
The Web user interface is still a work in progress.