Bug 508215

Summary:	Change "CONFIRMED" into "REPRODUCIBLE BY DEV"
Product:	[Websites] bugs.kde.org	Reporter:	Fernando M. Muniz <fernandommuniz>
Component:	templates	Assignee:	KDE sysadmins <sysadmin>
Status:	RESOLVED INTENTIONAL
Severity:	wishlist	CC:	nate, sheedy
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Arch Linux
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Fernando M. Muniz 2025-08-14 00:56:26 UTC

STEPS TO REPRODUCE
Changing a REPORTED bug into CONFIRMED because many users are experiencing.

OBSERVED RESULT
It's a wrong change because devs being able to reproduce the issue is what matters to produce a fix.

EXPECTED RESULT
Seeing a more precise name that wouldn't cause this situation.

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 6.4.4
KDE Frameworks Version: 6.17.0
Qt Version: 6.9.1
Kernel Version: 6.15.9-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 8 × 11th Gen Intel® Core™ i5-11300H @ 3.10GHz
Memory: 9 GB of RAM (8.1 GB usable)
Graphics Processor 1: NVIDIA GeForce GTX 1650
Graphics Processor 2: Intel® Iris® Xe Graphics
Manufacturer: LENOVO
Product Name: 82MG
System Version: IdeaPad Gaming 3 15IHU6

Comment 1 2wxsy58236r3 2025-08-14 08:03:42 UTC

What if we keep the status as "CONFIRMED" but only allow developers to confirm bugs (by adjusting the "canconfirm" permission)?

Comment 2 Fernando M. Muniz 2025-08-14 08:05:34 UTC

(In reply to 2wxsy58236r3 from comment #1)
> What if we keep the status as "CONFIRMED" but only allow developers to
> confirm bugs (by adjusting the "canconfirm" permission)?

That would also work.

Comment 3 Nate Graham 2025-08-14 14:01:51 UTC

Developers (and bug triagers) are already the ones who generally mark issues as confirmed. I'm not sure changing the semantics here to greater specificity would add much value, and additionally it would cause all the issues that are currently CONFIRMED but that were not confirmed by a developer or bug triager to become inaccurate.

As for only letting devs mark bugs as confirmed, in general we find that it's good to let the community itself help with bug triage, hence the fairly broad permissions granted to people with normal accounts. The levels of accidental mistake-making and deliberate vandalism are pretty low right now. If that changes, we can lock things down more, but until then, I think it would hurt more than it would help.