This is the approach I have been taking recently as well. I have set up an alert for test cycles with test cases and most of the time these are the only cycles I participate in.askgar said:Nah, I have a full time job as a software developer, this is something I do for extra money in my spare time. I tend to focus mostly on test case cycles, with most of my bugs being a side effect of test cases.
It feels like in this case the customer approving the bugs, wasn't the same person who defined the scope, so they didn't realise what was actually being tested.
Generally in those cycles the issues being approved straight away are obvious issues (usually with basic functionality being broken for everyone, or obvious UI issues) the ones that stay pending are usually because the customer needs to do further investigation to determine if something is a bug, an issue with the users environment, more information gathering required, etc. I tend to find in cycles with things being approved quickly, rejections tend to occur quickly as well, it is the more complex issues which hang around.