Bug 451935

Summary:	Bugs marked as resolved when marked as duplicate
Product:	[Websites] bugs.kde.org	Reporter:	Kjetil Kilhavn <kjetil>
Component:	code customizations	Assignee:	KDE sysadmins <sysadmin>
Status:	RESOLVED INTENTIONAL
Severity:	major	CC:	bcooksley, sheedy
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	unspecified
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Kjetil Kilhavn 2022-03-26 16:14:00 UTC

SUMMARY
When bug 445082 was marked as a duplicate it was also marked as resolved. That would be true if the bug it was marked as duplicate of was resolved, but this is not the case.
Duplicate (resolved): https://bugs.kde.org/show_activity.cgi?id=445082
Bug (confirmed): https://bugs.kde.org/show_bug.cgi?id=428112

OBSERVED RESULT
Bug closed as resolved when it is not resolved.

EXPECTED RESULT
Duplicates should not be marked as resolved until the bug they are marked as duplicates of is marked as resolved. They can either display their own status or the status of the bug they are marked as duplicates of - I have no strong opinion on that since the "Duplicate stamp" indicates that the resolution will be implemented for another bug.

SOFTWARE/OS VERSIONS
Not relevant

ADDITIONAL INFORMATION
I actually don't know if the status was set to resolved manually at the same time as the bug was marked as a duplicate, or if this is automated. So, this is potentially not a technical bug, but to my knowledge there isn't any way I can check that (without marking a reported bug as duplicate).

Ideally, bugs marked as duplicates should have the same status as the bugs they are marked as duplicates of.

Comment 1 Ben Cooksley 2022-03-26 19:19:10 UTC

This is expected behaviour and how the system is supposed to be used.

Duplicate bugs are considered Resolved as there is nothing further for a developer to investigate.
The reporter of the duplicate is added to the original bug as part of the resolution as duplicate process.