Hi, following up on a discussion with Matt Rogers, I'd like to suggest to change of behaviour in the BKO system. Currently, if a KDE member with sufficient karma creates a new bug report for _any_ KDE component, it will be automatically confirmed as "new". Seeing that KDE has expanded so much and has become so versatile during the last years, it's very unlikely that every KDE contributor automatically is an expert on all KDE components. Example: I (an Amarok contributor/expert) would create a bug report for KMail. I don't have the slightest clue about the internal workings of this application. For all practical matters, I should be considered a "normal user". Assuming that my potential bug report for KMail is automatically valid is a fallacy, IMHO. It's well possible that my report is invalid, for lack of knowledge, or other reasons.
#189500 is such a good example of this.
I'm looking to see what would actually be required for this to be implemented. It may require a major change to how bugzilla is currently set up.
*** Bug 215883 has been marked as a duplicate of this bug. ***
*** Bug 246025 has been marked as a duplicate of this bug. ***
Hi, just two notes: 1. in the un-guided bug reporting form (like https://bugs.kde.org/enter_bug.cgi?product=konsole), I can explicitly set the initial status of the report being created to "UNCONFIRMED" when the advanced fileds are shown. 2. The Web Service API also allows for explicitly setting the initial status . That means DrKonqi can ensure all crash reports created by it are set as "UNCONFIRMED" initially, even when they are created by users with previliege. That only needs a simple patch.
I've now changed bugzilla's workflow to only allow unconfirmed as initial state. Maybe this fixes it?