How to create a release record

There are the following ways to create a release record:

Search for	Example	Results
A single word	`cat`	Topics that contain the word "cat". You will also find its grammatical variations, such as "cats".
A phrase. You can specify that the search results contain a specific phrase.	`"cat food"` (quotation marks)	Topics that contain the literal phrase "cat food" and all its grammatical variations. Without the quotation marks, the query is equivalent to specifying an OR operator, which finds topics with one of the individual words instead of the phrase.

Search for	Operator	Example
Two or more words in the same topic	`AND` `and` `+` (plus symbol) `&` (ampersand)	`cat AND dog` `"cat food"+milk` `"cat food"&"dog food"`
Either word in a topic	`OR` `or` `\|` (pipe)	`cat OR dog` `cat \| dog`
Topics that do not contain a specific word or phrase	`NOT` `not` `!` (exclamation point)	`NOT cat` `! dog`
Topics that contain one string and do not contain another	`^` (caret)	`cat ^ mouse`
A combination of search types	`( )` parentheses	`cat + (dog \| mouse)` `cat \| dog + (! mouse)`

In Release Management

From the main menu, select Build > Release.
Click New. Service Management displays the New Release form. Service Management does not assign a release ID until you save the record.

Complete the Release Details section.

This section contains basic information about the release that helps efficient release management.

Field	Description
Title	A title for the release. Best practice: choose a meaningful, descriptive, and relatively short title. Titles are often the only identification used in selection lists and in other areas to identify components.
Release type	The type of release: Minor Major Emergency
Description	A description that captures the details of the release.
Service	The service affected by the release. Using the out-of-the-box configuration, Service Management automatically sends the service owner a notification at certain parts of the workflow. In addition, the relevant support groups are automatically notified when the release enters the early life support phase.
Category	The category of the release. Service Management uses the category to classify release records.
Release model	A collection of predefined values. Selecting the model automatically populates the relevant fields and creates the task plan necessary to complete the release. In the drop-down list, models are filtered according to the release type and service. After you select a release model, you may overwrite any field values which the model provided. If you do so, saving the record saves the overwritten field values, and not the values which the release model provided.
Reason for release	The reason for the release. Choose the reason that most closely matches the purpose of the changes to be included.

Complete the Request for execution section.

Field	Description
Latest execution date	The date and time by when the release is to be complete.
Urgency	The urgency value describes how important the issue is for the customer. Service Management uses the urgency value to calculate the priority for the implementation.
Justification	The justification for the release. What may happen if the release is not implemented? Best practice: Be as specific as possible.

Field

Description

Latest execution date

The date and time by when the release is to be complete.

Urgency

The urgency value describes how important the issue is for the customer. Service Management uses the urgency value to calculate the priority for the implementation.

Justification

The justification for the release. What may happen if the release is not implemented?

Best practice: Be as specific as possible.

Complete the User options section.

This section contains any user options. These are cloned from the model for the record.

For more information, see User options.
Click Save.