Bug 494441 - RESOLVED and NEEDSINFO have resolutions that don't make sense
Summary: RESOLVED and NEEDSINFO have resolutions that don't make sense
Status: CONFIRMED
Alias: None
Product: bugs.kde.org
Classification: Websites
Component: general (other bugs)
Version First Reported In: unspecified
Platform: Arch Linux Linux
: NOR minor
Target Milestone: ---
Assignee: KDE sysadmins
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-10-10 13:19 UTC by Filip
Modified: 2024-10-11 19:24 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Filip 2024-10-10 13:19:11 UTC 
SUMMARY
Curate set of statuses for RESOLVED and NEEDSINFO to make them fit better. I made a suggestion below, you can of course modify something to make it better if you decide to accept the change.

OBSERVED RESULT
Currently both, RESOLVED and NEEDSINFO, have all these statuses and I don't think all of them are appropriate for both of them:
Fixed
Not a bug
Intentional
Later
Remind
Duplicate
WorksForMe
Moved
Upstream
Downstream
WaitingForInfo
Backtrace
Unmaintained

EXPECTED RESULT

RESOLVED:
Fixed
Not a bug
Intentional
Later
Remind -- Not sure the use case here. Can Later be used for both?
Duplicate
WorksForMe
Moved
Upstream
Downstream
Unmaintained

NEEDSINFO
Upstream
Downstream
WaitingForInfo
Backtrace
Comment 1 Nate Graham 2024-10-11 18:43:08 UTC 
So basically, we should remove:

FIXED WAITINGFORINFO
FIXED BACKTRACE

NEEDSINFO NOTABUG
NEEDSINFO INTENTIONAL
NEEDSINFO LATER
NEEDSINFO REMIND
NEEDSINFO DUPLICATE
NEEDSINFO WORKSFORME
NEEDSINFO MOVED
NEEDSINFO UPSTREAM
NEEDSINFO DOWNSTREAM

Seems reasonable, if it's possible.
Comment 2 Ben Cooksley 2024-10-11 19:24:14 UTC 
Unfortunately that would require some very custom logic to support - Bugzilla does not allow us to limit the Resolution that is chosen for bug statuses that are set as Type=Closed (which is both FIXED and NEEDSINFO)