The following page documents the meaning of the bug fields, among which the Bug Status. It documents the possible reasons corresponding to Closed bugs, specifically at this time FIXED, INVALID, WONTFIX, DUPLICATE and WORKSFORME. https://bugs.kde.org/page.cgi?id=fields.html#status But it does not document the meaning of 'RESOLVED UPSTREAM'. In particular this does not mean that the bug has been resolved upstream as is illustrated by this bug: https://bugs.kde.org/show_bug.cgi?id=328437 Actually there are quite a few other reason omissions: LATER, REMIND, MOVED, DOWNSTREAM, WAITINGFORINFO, BACKTRACE and UNMAINTAINED. Ironically 'CLOSED' is also not mentioned in the list of statuses corresponding to closed bugs ;-) Reproducible: Always
*** Bug 329486 has been marked as a duplicate of this bug. ***
Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone!
Dear Bug Submitter, This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand. Thank you for helping us make KDE software even better for everyone!
It's documented at https://community.kde.org/Get_Involved/Issue_Reporting#Understand_what_the_resolution_statuses_mean
Either there should be a link to that page from the status help page (https://bugs.kde.org/page.cgi?id=fields.html#bug_status), or its content should be duplicated to the status help page. Also that still leaves LATER, REMIND, MOVED, WAITINGFORINFO, BACKTRACE and UNMAINTAINED as undocumented.
We can't change that page as it requires upstream changes in Bugzilla itself. Duplicating its entire content elsewhere is not reasonable and would create a maintenance headache. This is fine as is IMO.