When comparing GitLab issues vs Fossil, the Slant community recommends Fossil for most people. In the question“What are the best self-hosted bug trackers?” Fossil is ranked 3rd while GitLab issues is ranked 4th. 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 Good web UI
GitLab's UI is clean and intuitive. Each view is designed to not fill the screen with useless information.
It displays the activity in a feed-type way in the most prominent part of the view. On top of that, there's a toolbar with buttons which can filter this feed by pushes, merge events or comments.
On the left, there's a menu that displays all the links that take you to the different views. For example, a file directory which displays all the files in that repo, a commit view which displays all the commits in cronological order, a network and a graph view that display important information graphically etc...
All these details make GitLab's UI extremely intuitive and easy to use, no view is overflown with information and every view displays only the most useful and crucial information needed at that time.
Pro Issues can have weight
You can set the weight of an issue during its creation (from 1 to 9) to get a better idea of how much time, value or complexity a given issue has.
Pro Comes with integrated CI/CD solution
GitLab CI makes it easy to set up CI and deployment for projects in GitLab. It supports parallel testing, multiple platforms, Docker containers and streaming build logs.
Pro Regular updates
GitLab is being constantly worked on and has a new release every month on the 22nd. Updating is also very easy through a single upgrade script.
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 Search functionality is not that refined
While you can search for users or projects, you cannot search for a filename. This makes GitLab's search one of the weak points in an otherwise great tool.
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.