Frank,
Providing the extra level of triage is critical to our teams success. We have considered different approaches to opening up our bug tracking system over the years and the fundamental problem is that the signal-to-noise ratio is *way too high*.
This is frustrating for users that know what they are doing (like yourself) but critical to do so that we don’t offload the triage step from the support team to the development team; who suddenly spends 8 more hours a week triaging bugs instead of implementing enhancements or fixing issues.
We have discussed the possibility of a “core” group of members that have access to a shared tracking resource but wasn’t launched due to resource restrictions. Any new effort we start will require someone to take care of it and facilitate that communication and we don’t have the man-hours to spare at the moment.
This may be something we look at again at the end of this year or early next though, especially if the user demand is there for it.
Ultimately we want to do right by our users but can’t sacrifice critical team resources to do it; because the end result there will be a poorer release and we know ultimately you guys wouldn’t want that.