"Sirius" was still set as the Bugzilla product. After removing this entry, the Bugzilla related buttons vanished. So at least the buttons don't confuse users anymore.
PMI should be tweaked to allow setting other bug trackers than Bugzilla. @cguindon can your team take a look?
IMHO, allowing setting other bug trackers doesn't make sense and is not a requirement.
With GitLab and GitHub, every repository has a corresponding issue tracker. There is no longer any notion of a single issue tracker. Our tendency is to move more of the metadata closer to the project content. In the case where a project has multiple repositories, they can point folks to a specific issue tracker in their README or CONTRIBUTING guide.
Surely the PMI should have a metadata entry for the Bug reporting tool that the page should format appropriately to to the chosen technology?
"The bug reporting tool" doesn't make sense any more. Every GitHub and GitLab repository has its own issue tracker and basically every potential contributor in the world knows and expects to find them there.
Furthermore, while it may have been true in the early days of the PMI (we were still using CVS at the time), I do not believe that the PMI is the primary means by which folks find our projects. In a world where GitHub exists (and has basically won), folks find the code first. This is why the EMO has been pushing projects to put more metadata directly in their repositories: this is where folks find it.
If your project is still using Bugzilla, then the EMO's strong recommendation is that you indicate this in the CONTRIBUTING or README file (FWIW, the documentation generator will automatically add a link to your project's Bugzilla if product/component information is specified in the metadata).
The Bugzilla integration is not hardwired, it is entirely based on the configuration in the project metadata as discussed. I believe that this issue has been addressed and am closing it.