|
|
|
[
Permlink
| « Hide
]
Strife Onizuka added a comment - 21/May/08 05:01 PM - edited
Yes it would be interesting but I don't think it would be used much. How would a user feel to have their "Showstopper" marked "Low" priority? No Linden is going to want to use the feature for risk of the flack. Hope springs eternal when you don't tell them it's a low priority but then when the spring does dry up, it really dries up. It's a double edged sword.
I think splitting it out like this means that the existing Priority field would become essentially useless. That's fine with me; I'd much rather see SOME priority field get some use... but we might as well delete the existing field while we're at it.
@Lex: Can you elaborate on why you think this would render the existing field useless?
Sure. We'd have two fields, "Priority" and "Linden Priority". "Priority" would be filled in by the community and would be subject to the kinds of change-wars that already happen. It'd have no bearing on the actual priority Linden assigns to the issue internally, because that's what "Linden Priority" is for. As Ramzi Linden put it, "Priority is mostly used to reflect how much an issue affects the reporting person."
I'm fine with "Priority" being mostly useless, though, if we get a field that actually gives us some idea of the priority Linden treats the issue with. As it stands, especially with Thank you for your ideas and suggestions. Being that this is a tool that would be used only by Lindens, we discussed the need and applications for such a tool. At this time, we do not see implementing this.
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||