December 11, 2009

Escalation Rules in TestTrack

Helix ALM
Escalation rules allow you to evaluate a certain condition on a continuous, scheduled basis. The most common use for escalation rules is to prevent inactivity on items. For example, every day at midnight, check for any items that have not been modified in the last 3 days. Escalation rules also allow you to configure an action or actions to perform on any item that matches the criteria, which is specified in the form of a filter. When using escalation rules to prevent inactivity, creating the correct filter may appear to be a challenge, but in reality they are pretty easy. If you are simply looking for general inactivity, use the "Last Date Modified" restriction. You probably want to also add the "State has an attribiute of Open" criteria to the filter. Filters can also test for workflow inactivity, which can ensure a critical item is kept moving along in the process. If you need to test for the time that an item has been in a particular state, then you restrict based on the date of the last occurrence of the event that would have moved the item into that state. Of course, you also need to make sure that the item is still in that state. The following images illustrate both filters mentioned in this article. [gallery link="file"] The first example returns any defect that is in an "open" state and has not been modified in any way for 3 days. The second example returns any item that is in the Fixed state and has been there for at least 3 hours.