Add to Chrome
Add to Edge
Add to Firefox
Add to Opera
Add to Brave
Add to SafariWhen comparing Fossil vs Codegiant, the Slant community recommends Codegiant for most people. In the question“What are the best bug/issue tracking tools for small development teams?” Codegiant is ranked 8th while Fossil is ranked 10th. The most important reason people chose Codegiant is:
Also provides access control to repositories.
Specs
Question 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 Collaboration
Also provides access control to repositories.
Pro User friendly
The user interface is very simple and intuitive.
Pro Documentation tool
Create knowledge bases, API documentation, status pages, product roadmaps, etc.
Pro Import repositories
Easily import repositories from Github, Bitbucket, hosted Git servers, or SVN.
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.
