---
sourceDocument: Australia IT Service Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/it-service-management

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia IT Service Management

ft:clusterId :

    - itsm

bundleId :

    - itsm

workflow :

    - Technology


---

# Define a release in Release Management

# Define a release in Release Management {#ariaid-title1}

Release version: Australia  
Updated March 12, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
During the release planning process, release managers define the type of the release
(major, minor, and so on.), schedule of the release (planned start and end dates), required
phase, phase tasks, and the scope.

## Before you begin

Role required: release_v2_admin

## Procedure

1. Navigate to AllReleaseProducts.
2. Open the product to which you want to add a release.  
   If a release belongs to no product or more than one product, you can directly
   navigate to ReleaseReleases to define the release. You need not define a release in the
   context of a product.
3. In the Releases related list, click New.
4. On the form, fill in the fields.  
   {#t_DefineARelease__table_klk_nvr_pjb__entry__2}

   | Field | Description |
   |-|-|
   | Number | Auto-generated unique identifier for the release. |
   | Release Type | Type of the release such as Major, Minor, Upgrade, Patch, or others. |
   | Priority | Priority of the release such as Critical, High, Moderate, or others. |
   | State | State of the release such as Draft, Work in progress, testing, or others. If you want to customize the options in this list, reach out to your admin. Custom states can be added according to the default state categories of the release table. [Learn more about the default states of the release table.](https://servicenow-prod.fluidtopics.net/ywOaQex4AubM1sSYyv2mXg "Understand how the different states of the Release [rm_release] and Release Task [rm_task] tables are configured by default. Use this information to customize the states according to your organizational release processes.") |
   | Percent complete | Progress of the release as a percentage of the whole. |
   | Short description | Brief description of the release. This description helps in identifying this release from a list of releases. |
   | Description | Details of the release. |
   | Planned start date | Tentative start date of the release. |
   | Planned end date | Tentative end date of the release. |
   | Planned duration | Duration of the release in days. When you submit the form, this field auto-populates based on the values of Planned start date and Planned end date. |
   [Table 1. Release form]

   {#t_DefineARelease__table_klk_nvr_pjb}
5. Click Submit.

## What to do next

* Attach documents such as release and deployment plans, installation manuals, and training documentation to a release. For more information, see [Add and manage
  attachments](https://www.servicenow.com/docs/access?context=t_AddingAnAttachment&version=australia&pubname=australia-platform-user-interface&ft:locale=en-US).

* Releases can have child releases. So, you can group minor releases under major releases. Add a child release by clicking
  New in the Releases related list in the
  Release form.

* [Define a release phase in Release Management](https://servicenow-prod.fluidtopics.net/CmlNEMPVh7DBClS84NAcRw "Define a release phase to represent the different stages of work required to complete your release.").
* [Define scope of a release in Release Management](https://servicenow-prod.fluidtopics.net/AVYzSTrtFpYq0e3mgUK2qA "Add projects, epics, stories, enhancements, and defects to define the scope of a release.").
{#t_DefineARelease__ul_rcx_pgs_pjb}

*[\>]: and then