Thread:Talk:Git/Workflow/Bugzilla

The page lacks instructions about what to do with bugzilla. The only relevant passages are: How to become a MediaWiki hacker says: I don't think it makes sense to have the code review queue for open commits on two separate tools?
 * If your commit addresses a bug in Bugzilla, please comment on that bug to note that the commit is in the merge queue, and link to its changeset in Gerrit.
 * If you merge a commit that references a Bugzilla bug, please go to that bug and mark it RESOLVED: FIXED and reference the merge ID.
 * Post a link to your Gerrit changeset in the appropriate bug report in Bugzilla with gerrit, and mark it with the patch and patch-need-review keywords.

What we're seeing is that most people mark the bug as fixed as soon as they commit the fix (otherwise they forget to), the dev who merges definitely marks as resolved fixed (although sometimes they forget) and then when further tested should be marked as verified fixed (by the reporter) or reopened. It's very confusing what one is actually supposed to do though.