When comparing Fossil vs MaxiBug, the Slant community recommends Fossil for most people. In the question“What are the best bug/issue tracking tools for small development teams?” Fossil is ranked 10th while MaxiBug is ranked 11th. The most important reason people chose Fossil is:
If you need a (distrubuted) SCM, Fossil comes with a built-in SCM, a wiki and issue tracker.
Specs
Ranked in these QuestionsQuestion Ranking
Pros
Pro DSCM + issue tracker + wiki
If you need a (distrubuted) SCM, Fossil comes with a built-in SCM, a wiki and issue tracker.
Pro Self-contained file
The data is stored in one single file. No file structure distributed over a bunch of folders.
Pro Multi platform
The executable is provided for multiple platforms, e.g. Linux, macOS, Windows.
Pro Easy to install
The Fossil application contains one single file. No need to install dependencies.
Pro Free
Pro Drag & Drop
Images can be dragged and dropped on the Issue form.
Pro Git support
From version 1.1.0 in the Issue form the "Git history" tab can be selected, and by pressing the sync button the Git history for an issue can be retrieved.
Pro Single exe
All that is needed is a single exe (file size less than 3 MB) and a PostgreSQL server, the database will be created automatically.
Cons
Con Ticket comments can't be edited
While a ticket can have multiple comments added to it, and (separately) also attachments — if the users have the right permissions — it is impossible to edit a comment after submitting it. This is probably why a comment must be previewed before it can be submitted.
Con PostgreSQL knowledge needed
There should be at least one person in the team that can administer a PostgreSQL server with user roles and rights.
Con Virus warning
Might give a false virus warning on some Windows versions when using the Edge browser, try with Chrome instead.
If someone would like to sponsor a paid authenticode certificate this might be solved, please leave a comment!