User:Victor Grousset - tuxayo/Bugzilla vs GitLab

Pros for GitLab (libre version)

merge requests
free QA tools using the continuous integration that would automatically run against every new patch (merge request)
editing comments
better review UI and diff display
trivial patches doable in the web UI
tells if the merge request non longer applies
upvoting comments
the UI for upvoting issues is clear which will make this feature used way more
being able to easily unsubscribe from the notifications of a bug without notifying everyone else (so we spam the others when muting the notifications ^^")
- Bugzilla non-obvious way: preferences → "Ignore Bugs" input
big patches that doesn't timeout the webserver
threads to not have one discussion make the whole comment history unreadable

Pros for Bugzilla

Dependencies between bugs
GitLab has an open core business model which makes them restrict the libre version. Including being able to set dependencies between bugs
- Still not much restricted. So it still have a feature set that outranks or matches more or less every other forges
Dependency graph (GitLab doesn't have it)
Being able to go to any bug that has patches an add them. That's seamless teamwork that is not that straightforward in GitLab

2024 Update: infos about another possibility: Phorge (fork of Phabricator)

Pros:

Dependencies between bugs
Dependency graph (see the 2nd image here: https://codeberg.org/forgejo/forgejo/issues/446#issue-252623)

Stuff to rethink when going to any tool

«The main thing is replicating the signoff/qa workflow in gitlab. That is the thing that will stop any move. If we can find a way to have everything needing a signoff and a qa approval before it can be merged, then gitlab would be great» --Chris 18:43, 17 August 2018 (EDT)