**aklapper** wrote on `2014-07-29 21:51:47 (UTC)`

>>! In T168#56, @Waldir wrote:
> I stand by my proposal to have a severity/impact dual-axis priority measure, with the highest priority items at the top right of the resulting space.

I'd like to see this in practice somewhere. It could work but I haven't see any tool implementing this.

> I agree the current definition of severity isn't ideal, but it's certainly a good start.

I don't see how it's "a good start".

> For example, the "important area to whom" question can be defined, say, in terms of the WMF's strategic goals, or the Engineering team

If the several stakeholders can somehow agree on something, okay. Again, designers might have a different interpretation of "major issue" than a performance engineer (maybe a bad example if it's unlikely that one bug report will touch both design and performance).

> getting rid of the "unspecified" value

(The Severity field in Bugzilla has no "unspecified" value - that's the Priority field.)

> and assigning a mid-range value by default (maybe "enhancement", based on the 60% number cited above?) could help here.

Enhancement will be expressed by the "Priority" value "Wishlist" in Phabricator. Also, "enhancement" is unrelated to any Severity/Impact. Instead it is a boolean value on its own. (That enhancement request to replace the joystick by a steering wheel in the car that we produce can be pretty severe if all other competitors ship that already and if we'd go bankrupt). It is wrong that Bugzilla has "enhancement" as a value in its Severity field.

> I proposed impact as a measure of how many people the issue annoys.

I don't see how "many people" can be defined. Estimation must be based on something, otherwise I'd call it wild guessing.

> I just think two reasonably objective measures with sane defaults are better than a single, subjective priority measure that we often won't be able to agree on

I miss how to concretely achieve such "objective measures" because currently we don't have them. If you can draw such concrete values and add them to the discussion here, that would be awesome. Right now it feels like "things aren't great, we can improve them" but I don't see a clear and specific proposal. And I miss why it's "better" - usecases.