When comparing Taiga.io vs Fossil, the Slant community recommends Fossil for most people. In the question“What are the best self-hosted bug trackers?” Fossil is ranked 4th while Taiga.io is ranked 6th. 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.
Ranked in these QuestionsQuestion Ranking
Pro Supports both Kanban and Scrum modes
User stories can be organized in both Kanban and Scrum task management systems.
Pro Free and open source
Taiga is licensed under GPL with source code available on GitHub.
Pro Simple to use
Pro Comprehensive Agile software development toolset
Taiga tries offering a complete Agile software development toolset. It includes complete solutions for issue tracking, videoconferencing, documentation (in the form of a wiki) and either a backlog or a Kanban board for managing user stories.
Pro Built-in wiki
Each project has a wiki. It has Markdown support as well as a WYSIWYG editor.
Pro Built-in issue tracking
Taiga has built-in issue tracking tools. The issues can be organized by user-defined type, severity, priority, creation date, assignee, creator, tags as well as filtered by subject. Taiga can also integrate with GitHub, GitLab and BitBucket.
Pro Built-in video conferencing tools
Integrates with either AppearIn or Talky to provide a video conferencing solution.
Pro Export/Import feature
You can extract all your data from one Taiga instance and move it to another one. You can read more here.
Pro Migration from RedMine
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.
A Fossil repository is contained in a single file.
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.
Con Too much functionality for small projects
While it's possible to disable any unwanted features (modules), the amount of functionality that's present might be more than a small, short-term project needs.
Con Can be overwhelming at first
Taiga presents users with a lot of information and functionality right from the beginning with little guidance. Figuring how stuff works might take a bit.
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.