• 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-401
Type: New Feature New Feature
Status: Open Open
Priority: Normal Normal
Assignee: Unassigned
Reporter: Fluf Fredriksson
Votes: 6
Watchers: 5
Operations

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

Assign Linden resources to maintaining the public JIRA

Created: 27/Nov/07 03:59 AM   Updated: 15/Oct/08 09:40 AM
Return to search
Component/s: jira.secondlife.com
Affects Version/s: Not Versioned
Fix Version/s: None

Last Triaged: 13/Oct/08 09:40 AM
Linden Lab Issue ID: DEV-6664


 Description  « Hide
The JIRA currently has well over 2,000 open issues listed.
This has multiple effects:
Because items are hard to find many duplicates are posted. An item with 20 votes is just as important as an item with 20 duplicates, but the later is harder to identify.
Developers are presumably wary of using the JIRA to find problems to resolve because of the sheer volume.
New users are wary of using the JIRA because of it's sheer scale.
Voting is ineffective while votes are cast across many related / duplicate issues and those votes are not transferred to issues once a duplicate is identified and linked.

Rather than suggest a new voting system or some reform of the JIRA that only it's creators can code. Assign more resources to maintaining the existing JIRA. If one person spent all day, every day identifying duplicates, closing non or out dated issues, creating and adding to meta issues and so on, the JIRA could be considerably compressed and be of much more use to both users and developers. That person would also be very well placed to suggest new categories or other improvements within the existing framework. The same person would also be an excellent point of contact within LL when trying to identify the current main issues.

This is something that in theory any user can do, but clearly in practise it isn't happening enough or with consistency. It's going to take some kind of paid allotted time to sift through and it seems wiser to have someone on the Linden side doing the linking and closing of related issues.

Note: Please link related issues rather than just close them without linking. It's important to see that 20 people opened the same kind of entry and adds weight when prioritising the main issues.



 All   Comments   Change History      Sort Order: Ascending order - Click to sort in descending order
Fluf Fredriksson made changes - 27/Nov/07 04:02 AM
Field Original Value New Value
Description The JIRA currently has well over 2,000 open issues listed.
This has multiple effects:
Because items are hard to find many duplicates are posted. An item with 20 votes is just as important as an item with 20 duplicates, but the later is harder to identify.
Developers are presumably wary of using the JIRA to find problems to resolve because of the sheer volume.
New users are wary of using the JIRA because of it's sheer scale.
Voting is ineffective while votes are cast across many related / duplicate issues and those votes are not transferred to issues once a duplicate is identified and linked.

Rather than suggest a new voting system or some reform of the JIRA that only it's creators can code. Assign more resources to maintaining the existing JIRA. If one person spent all day, every day identifying duplicates, closing non or out dated issues, creating and adding to meta issues and so on, the JIRA could be considerably compressed and be of much more use to both users and developers. That person would also be very well placed to suggest new categories or other improvements within the existing framework.

This is something that in theory any user can do, but clearly in practise it isn't happening enough or with consistency. It's going to take some kind of paid allotted time to sift through and it seems wiser to have someone on the Linden side doing the linking and closing of related issues.

Note: Please link related issues rather than just close them without linking. It's important to see that 20 people opened the same kind of entry and adds weight when prioritising the main issues.
The JIRA currently has well over 2,000 open issues listed.
This has multiple effects:
Because items are hard to find many duplicates are posted. An item with 20 votes is just as important as an item with 20 duplicates, but the later is harder to identify.
Developers are presumably wary of using the JIRA to find problems to resolve because of the sheer volume.
New users are wary of using the JIRA because of it's sheer scale.
Voting is ineffective while votes are cast across many related / duplicate issues and those votes are not transferred to issues once a duplicate is identified and linked.

Rather than suggest a new voting system or some reform of the JIRA that only it's creators can code. Assign more resources to maintaining the existing JIRA. If one person spent all day, every day identifying duplicates, closing non or out dated issues, creating and adding to meta issues and so on, the JIRA could be considerably compressed and be of much more use to both users and developers. That person would also be very well placed to suggest new categories or other improvements within the existing framework. The same person would also be an excellent point of contact within LL when trying to identify the current main issues.

This is something that in theory any user can do, but clearly in practise it isn't happening enough or with consistency. It's going to take some kind of paid allotted time to sift through and it seems wiser to have someone on the Linden side doing the linking and closing of related issues.

Note: Please link related issues rather than just close them without linking. It's important to see that 20 people opened the same kind of entry and adds weight when prioritising the main issues.
lindenrobot made changes - 29/Nov/07 04:26 PM
Linden Lab Issue ID DEV-6664
Rob Linden made changes - 21/Dec/07 11:42 PM
Workflow jira [ 17235 ] jira-2007-12-19 [ 18982 ]
Rob Linden made changes - 22/Dec/07 12:18 AM
Workflow jira-2007-12-19 [ 18982 ] jira-2007-12-21 [ 19405 ]
Rob Linden made changes - 23/Dec/07 12:42 AM
Workflow jira-2007-12-21 [ 19405 ] jira-2007-12-22a [ 49630 ]
Fluf Fredriksson made changes - 17/Jan/08 01:59 PM
Summary Assign Linden resources to maintaining the JIRA Assign Linden resources to maintaining the public JIRA
Alexa Linden made changes - 15/Oct/08 09:40 AM
Last Triaged 13/Oct/08 09:40 AM
Sue Linden made changes - 13/Nov/08 11:55 AM
Workflow jira-2007-12-22a [ 49630 ] jira-2008-11-14 [ 79211 ]
Sue Linden made changes - 13/Nov/08 04:19 PM
Workflow jira-2008-11-14 [ 79211 ] jira-2008-11-14a [ 83775 ]