Hi Everyone, Michael came up with an idea for hard hacks that I liked. Here is the proposal: a) each QA "staff" member gets to nominate one bug to hard hacks at a time b) that member monitors the bug occasionally and once it is fixed they can put another one on the list c) in order to track we could use the QA Contact Field since no one else uses that field vs. whiteboard where anyone and everyone edits. We could use it in one of two ways: - have a dedicated QA member that we assign to (one) and then that basically tells the developers "this is a hard hack" - each individual member of QA puts their own name in there so then the developers know who put the bug as a hard hack I am also open to the idea of just adding a whiteboard status of HardHack. Today at the conference call they had done all but 1 of them and asked for more, I was unprepared to give more. We should try to keep that list constantly at 5-7 bugs. Probably something that we should discuss next week during our call but we need to get a method down so that developers can tackle these bugs. Best Regards, Joel