Share this page
Precedence of Dependencies Among Multiple Override Rules
All of the specified dependencies (filters) of an override rule must be satisfied to apply the rule. If all the dependencies for more than one override rule are met, only the override rule with the highest precedence takes effect. (However, see also Precedence of Results for Override Rules for more information.)
The precedence among override rules whose dependencies are all met is based on which combination of dependencies is met for each of the override rules. Table 7-2. Override rule precedence based on which dependencies are met shows the order of override rule precedence based on which of the five dependencies, indicated by X's, are met.
Note that whenever an override rule B has a subset of the dependencies of an override rule A, and all the dependencies of rule A and rule B are met, rule A takes precedence over rule B, so the specified results of rule A take effect. In other words, more restrictive rules take precedence. For example, only precedence 1 requires that all five of the rule's dependencies be met by a time sheet line and a resource, whereas lower precedence 2 imposes no requirement upon the Title of the resource. Similarly, for precedence 11, the Work Item Type of the time sheet line and the Title of the resource are specified, whereas only the Work Item Type is specified for lower precedence 12.
Note: If a particular project is integrated with Time Management and its Cost and Effort policy specifies that a project representative must approve time for the project, that policy supersedes any override rules for determining approvers, except where the override rule applies to a particular task. For more information about precedence of approvers, see the Time Management User Guide.
Consider the following example cases and the dependencies for two override rules named Rule A (with precedence 4) and Rule B (with lower precedence 6), shown in Table 7-3. Example of precedence of dependencies among override rules. For precedences 4 and 6, the Title of the resource does not matter (see Table 7-2. Override rule precedence based on which dependencies are met), so it is not considered in the example.
In the following examples, assume that, for all time sheet lines, the Work Item Type is Request and the Work Item Set is Key Release.
Case One
An engineer from Development is working on the 30122 work item (Alpha Test) of the Key Release request. The Work Item Type, Work Item Set, and Work Item dependencies for Rule A are met. So are the Work Item Type, Work Item Set, and Department (of Resource) dependencies for Rule B. Because Rule A has higher precedence, the engineer's time approver is set to Jim Grayson.
Case Two
An accountant from Finance is working on the 30122 work item of the Key Release request. The Work Item Type, Work Item Set, and Work Item dependencies for Rule A are met. The Department (of Resource) dependency for Rule B is not met. As a result, the accountant's time approver is set to Jim Grayson.
Case Three
A programmer from Development is working on the Beta Planning work item of the Key Release request. The Work Item dependency for Rule A is not met. The Work Item Type, Work Item Set, and Department (of Resource) dependencies for Rule B are met. As a result, the programmer's time approver is set to Joan Bell.
Case Four
A consultant from Services is working on the Beta Planning work item of Key Release. The Work Item dependency for Rule A is not met. The Department (of Resource) dependency for Rule B is not met. Neither rule applies, so the consultant's time approver is his or her default time approver.
