Bug 13851 - Bug resolution descriptions (Status link) need customized, CODE_FIX, etc
Summary: Bug resolution descriptions (Status link) need customized, CODE_FIX, etc
Alias: None
Product: Other
Classification: Unclassified
Component: Bug Tracker (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: Bug Me Administrator
Depends on:
Reported: 2009-07-27 09:35 UTC by Duncan
Modified: 2020-05-13 18:59 UTC (History)
2 users (show)

See Also:
Kernel Version: -
Regression: No
Bisected commit-id:


Description Duncan 2009-07-27 09:35:13 UTC
This bug is being filed based on the the resolution of bug 13750.

A fix showed up in the tree (for on-tag 2.6.31-rc4) without further bug interaction.  So I go to resolve the bug, and wonder whether that's CODE_FIX or PATCH_ALREADY_AVAILABLE.  So I click on the status link, expecting to find a helpful description I can use.

But all I see is the generic bugzilla documentation, fixed, etc, no bugzilla.kernel.org customized documentation to match the customized resolutions, therefore no description of CODE_FIX and no description of PATCH_ALREADY_AVAILABLE to help me decide which is appropriate.

It'd be helpful to know what each of the resolutions actually means in the bugzilla.kernel.org context.
Comment 1 Duncan 2019-04-19 05:11:25 UTC
The bug remains today.  The status link still apparently resolves to generic status help, while PATCH_ALREADY_AVAILABLE and CODE_FIX are still apparently kernel bugzy specific, and aren't covered.
Comment 2 Brian Norris 2020-05-13 18:59:36 UTC
I guess this is the place for these status descriptions?


I agree, it's kinda confusing though. I'm only just learning my way around bugzilla and I had the same question... It feels like there's a lot of UX improvements to be had in bugzilla, around pointing at the docs, etc. I've also found this page useful, but it's not linked anywhere from bugzilla.kernel.org itself:

For your case (fix was developed apart from the bug in question), PATCH_ALREADY_AVAILABLE is probably the right answer.

Note You need to log in before you can comment on or make changes to this bug.