• All submissions to this site are governed by Second Life Project Contribution Agreement. By submitting patches and other information using this site, you acknowledge that you have read, understood, and agreed to those terms.
Issue Details (XML | Word | Printable)

Key: WEB-668
Type: New Feature New Feature
Status: Resolved Resolved
Resolution: Won't Finish
Priority: Normal Normal
Assignee: Rob Linden
Reporter: Jacek Antonelli
Votes: 0
Watchers: 3
Operations

If you were logged in you would be able to see more operations.
3. Second Life Website - WEB

New "Linden Priority" field in PJIRA

Created: 21/May/08 02:41 PM   Updated: 15/Oct/08 10:02 AM
Return to search
Component/s: jira.secondlife.com
Affects Version/s: None
Fix Version/s: None

Issue Links:
Relates
 

Linden Lab Issue ID: DEV-15703


 Description  « Hide
The idea here is to discuss the desirability of a new field for PJIRA tasks, "Linden Priority", which would be used to convey the priority level as decided by the Linden programmer(s) assigned to the issue. This would be separate from the current Priority field, which reflects the view of the reporter / Resident community.

This was first proposed in the comments for WEB-659.



 All   Comments   Change History      Sort Order: Ascending order - Click to sort in descending order
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.

Lex Neva added a comment - 22/May/08 09:52 AM
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.

Jacek Antonelli added a comment - 22/May/08 10:51 AM
@Lex: Can you elaborate on why you think this would render the existing field useless?

Lex Neva added a comment - 22/May/08 11:21 AM
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 WEB-659, the field is largely meaningless. We don't have much at all in the way of guidance on priorities, and those of us that try to follow the guidelines as best we can open ourselves up to abuse from people who see us as somehow speaking for Linden. There's a lot of confusion as to just what the current priority field means, and that's because its purpose and the way it's currently used is pretty ambiguous. I'm in favor of this proposal if it's the way to get a useful, clearly-defined priority field.


Alexa Linden added a comment - 15/Oct/08 10:02 AM
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.