When comparing Aiveo vs Fossil, 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 Aiveo is ranked 18th. 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 Task/Agile board
Includes a task board to visualize your projects status.
Pro Simple, clean, modern interface
Pro Includes a free tier
Free for up to 5 users.
Pro Paid plans are relatively cheap
Paid plans start at just $10/month.
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.
Cons
Con Relatively new and not as feature rich as some competitors
Some of the bigger missing features are integrations with other systems. More reports, custom dashboards and importing and exporting of work items. For those that do not use these features it may not be a large issue, but for those that do, it could really limit the usefulness of this tool.
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.