Request baseline templates enable you to specify rules for selecting requests that will be used as input for creating a baseline from their related items. They comprise one or more rules that are made up from the following:
Request type.
Request status.
Baseline status code, which itself comprises one of the following keys:
EQS – specified state only.
SUP – specified state and upward.
When a baseline is created specifying a request baseline template and a set of starting parent requests, then all the requests that:
are related to those parent requests, and
match the template rules
will be collected together for processing.
The template rules will be processed in exactly the same way they are for item templates, that is, requests will be selected based on the type, status, and the baseline status code that was specified. For example, if a template had a rule that specified:
all requests of type PR,
at status ACCEPTED,
with the baseline status code EQS
then all the requests of type PR, at the status ACCEPTED only, would be used for inclusion into the baseline.
Once this list of requests has been determined, then only those items that are related to those requests with either an In Response To or, optionally, an Info relationship will be included in the baseline. However, because the baseline that is being created is a release baseline, only one revision of each item will be included in the baseline (not all revisions, as would be the case for a design baseline). This means, that even though the requests being selected may contain multiple revisions of the same item, the final baseline can only contain one revision of all these possible items.
To ensure that only one revision of an item is included in the final baseline in circumstances where multiple item revisions are related to requests, only the latest item revision will be selected using that item's pedigree.
When the baseline has been created, the requests that were used to create it will be related as In Response To that new baseline.