Original summary: "Clone This Bug" links no longer work as expected To reproduce: 1-click on a "Clone This Bug" link, e.g. https://bugs.kde.org/enter_bug.cgi?cloned_bug_id=94611 on https://bugs.kde.org/show_bug.cgi?id=94611 Actual behavior: 1-opens "First, you must pick a classification on which to enter a bug:" page 2-none of the selections leads to a form from which kdelibs can be selected 3-neither kdelibs nor kdecore is selectable as product/component Expected behavior: 1-enter bug page opens 2-summary is pre-filled 3-kdelibs is preselected 4-kdecore is preselected 5-all relevant else not needing change is pre-selected/pre-filled 6-comment/description has been filled with comment #0 from bug to clone from I tried several of the selections on the "First, you must pick a classification on which to enter a bug: page." <https://bugs.kde.org/enter_bug.cgi?classification=__all> None produced an expected way forward for a Bugzilla & KDE user of more than two decades. What lead to this was I was trying to use bug 94611 as a pseudo template to file a bug against kdelibs/kdecore, nothing to do with XML or XSD.
You can't clone a bug to a component that's closed, and kdelibs is closed to new bug entry, because it's been obsolete and unmaintained for 8 years.
So 94611 was a bad example. The issue applies to the whole project. It doesn't matter which bug one selects to try to clone. The same failure results by trying to clone bug 385135 or bug 460400 or bug 263562.
It's not a failure, though. When you clone a bug, you've always had to tell it where to make the new bug. The procedure for selecting where to file your bug report has gotten longer since we grouped everything into categories, but that was an intentional change that overall people have been very happy about. If this has had the side effect of adding an extra step when cloning a bug, it's just something we're going to have to live with, I'm afraid.
(In reply to Nate Graham from comment #3) > It's not a failure, though. When you clone a bug, you've always had to tell > it where to make the new bug. Maybe KDE's Bugzilla was errantly customized, but that's half the point of Bugzilla's cloning feature, automatically pre-filling multiple form fields, including product and component, without having to determine a correct pigeonhole that matches neither product nor component in a new bug input form. If cloning is to remain as useless as it now is, the "Clone This Bug" links need removal, not remaining broken.
There's nothing we can do here without making code changes to our Bugzilla instance, which Sysadmins have vetoed. So I'm sorry to say this is the way it's going to have to remain. Feel free to file an upstream bug report about it. Maybe Mozilla will fix it.
I seriously doubt upstream can fix what KDE customization broke.
We are using an officially supported Bugzilla feature to make the categories appear when choosing there to file a bug report; no code customization was involved. I would hope upstream is interested in improving the "Close this bug" use case when using that feature.
Hereyago: https://bugzilla.mozilla.org/show_bug.cgi?id=1795789 "Clone This Bug" links no longer work as expected
Thanks!