Each rule is entered into the Routing Rules page, which is located in .
The percent sign (%) in the Release, Platform, and Component fields of the New Routing Rule dialog box serves as a wildcard character that matches all characters. Using the percent sign by itself in all three fields would be the same as default routing; everything would be routed to the four inboxes specified in the dialog box, regardless of values for release, platform, and component.
Once a rule has been saved, it is entered into the Routing Rules page. This page is essentially a routing table for a particular product. Alternate product selections can be made using the Product list box at the top of the page.
The order of rules for a component is critical. Issue Manager routes issues by evaluating their current state, for example Unreviewed, against each rule in the table in order. As soon as Issue Manager finds a match, it executes the rule. If there is no match, it routes the issue according to the default rules. Default routing rules are applied only after all other rules for a given product have been applied.
Release 4.% in the Release field would match all Release 4 releases: 4.0, 4.1, 4.1.1, and so on.
For example, send issues that are related to Product A for all releases and all platforms to the Sonja - Dev inbox when the issue is ready for development, to the Mike - QA inbox when the issue is ready for QA, to the Product A request-for-enhancement inbox Dan -- Dev (Product A) when an enhancement is submitted, and to the Judy -Doc inbox when a documentation issue relating to the Show me component is reported.