The Future Of Resolutions

[timeless]

MattyT wrote:

> I'm still looking at getting customised resolutions in early in the 2.19
> cycle, so I thought I'd solicit feedback on the new resolution set.
> 
> Existing installations should have their resolution sets maintained
> (even if they've changed the hardcoding), but new installations will
> receive an updated set to reflect years of Bugzilla experience.
> 
> Without further ado, the following is my current plan:
> 
> FIXED A fix for this bug is checked into the tree and tested.
> WORKSNOW The problem was reproduced, but seems to have disappeared by
> changes not made on this bug.
> INVALID This is not a proper report.
> FEATURENOTBUG This is not a bug, it's a feature.
> NOTWORTHIT It should be fixed in a perfect world, but this isn't a
> perfect world, so it won't be. (probably should be deleted by OSS)
> DUPLICATE The problem is a duplicate of an existing bug.
> WORKSFORME All attempts at reproducing this bug were futile, reading the
> code produces no clues as to why this behavior would occur.
> MOVED The bug has been moved to another Bugzilla installation.
> MISSING When a bug report can't be dealt with because an external
> resource (eg a page at a URL) is missing. (NOINFO maybe, after sitting
> in NEEDINFO status)
> CAREFACTORZERO When the person responsible really just does not care.
> MUPPET The reporter is a muppet.
> 
> In particular, WONTFIX, REMIND and LATER are gone, and good riddance.

I've wanted:
CANTFIX - the problem indeed exists but can not be fixed by changes to 
the codebase
DONTFIX - the report was proper, but the module owner has indicated that 
the request should not be fixed/implemented

wrt MISSING, I'd rather that be a status instead of a resolution

Status:
Needs

"Resolution":
Info|Testcase|Patch|Translation|...