I work on a large product that is looking at RQM for test tracking (and later execution). One thing we currently struggle with is investigation of test failures.

We run tests on 60 boxes, and failures can often become a full time job for more than one person. Often the failures are problems with setup on boxes, but they still all need looking at.

One way of doing this that seems good would be to have a queue of "not looked at" failures. The ability to put your name against an entry in this queue while you look at the failure (it could take 2 minutes, or 2 days to track down) means other people can easily see what else they should look at without stepping on your toes.

It occurred to me that this sort of queuing thing could easily be auto-generated tasks or defects in RTC... It has ownership, a suitable api interface and the ability to show a list of outstanding work

Has this use-case been considered at all in RQM? Is it possible to have a piece of custom code run every time a new failure occurs?

(One thing that would need to happen, is filtering so that only one item is raised for a failure on all boxes - i.e. first failure of test 1 is on box A, task X is raised. Test 1 then also fails on box B but we don't want a new task as this should be done under the same task X)