Priority System for Enhancements

[Bill Barry]

Benton, Kevin wrote:
>
>> 	To assist this (or basically implement it), I'm going to be
>> prioritizing enhancements.
>>
>> 	P1 = We definitely want this. It's a major feature, and it's
>> obvious that it would be useful to everybody.
>>
>> 	P2 = We want this, but it's not totally clear or extremely
>> important.
>>
>> 	P3 = This isn't a bad idea, and maybe we'll want to implement
>> it at some point in the future, but it's not near-term roadmap
>> material. Some core Bugzilla developer may work on it.
>>
>> 	P4 = This isn't a terrible idea, but it's not important to our
>> long-term plans for Bugzilla. We would review a patch if somebody
>> posted it, but a core developer is unlikely to work on it.
>>
>> 	P5 = We basically never want this. If somebody implements it
>> and asks for review, we *might* look at it.
>>     
>
> I'm wondering - there are cases when it might be useful to use
> Enhancement_Urgent, Enhancement_Needed, Enhancement_Wanted,
> Enhancement_Not_Likely as the severity rather than changing the meaning
> of Priority based on the status?  I'm saying this because I know of a
> number of Bugzilla users that have service level agreements set up in
> such a way so that the customer determines severity and the developer
> determines priority.  
<snip>

This is exactly why bug 9412 needs to be done.