Guidance for creating requests

I have started to add my most relevant bugs from my internal lists. Without any particular guidance I have added the tags that I use to group the type of bugs that I had in my list. This to try to help you guys group functionalities together so that when you start touching a module you can quickly bring up all the bugs related to that module. But I think you guys should establish some guidance in terms of how you want bugs classified so that you can organize them more effectively.

e.g.
- Impact
- Urgency
- Function Group
- Performance
- Usability

etc.... Its really up to you to decide how you want them classified because as more power users get a hold of this you can get a barrage of bugs finding your way.

Jay had tried a couple of different systems to be able to classify bugs and keep his focus on the most important impactful ones, but it was always a struggle to keep them coming in in an organized way that was easy to pinpoint what are the most significant ones that will yield the best bang for the deveopment hours invested.

I noticed my last bug request was somehow retained for authorization, so I am going to stop adding more bugs until you guys can provide more guidance on how you want us to proceed, as I still have a few to go.