---
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 scope of a release in Release Management

# Define scope of 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  
Add projects, epics, stories, enhancements, and defects to define the scope of a
release.

## Before you begin

Role required: release_v2_admin

## Procedure

1. Navigate to AllReleaseReleases.
2. Click the release number for which you want to define the scope.
3. On the Release form, navigate to one of the following related lists.  
   * Projects
   * Scrum Epics
   * Scrum Stories
   * SAFe Epics
   * SAFe Features
   * SAFe Stories
   * Defects
   * Enhancements
   * Incidents
   * Problems
   * Changes

   {#t_ScopeARelease__ul_zw1_yjr_pjb}  
   Note:  
   To view the respective work items, ensure that the plugins Agile Development 2.0, Project Portfolio Management, Essential SAFe, and Portfolio SAFe are active.
4. Add a task to the related list.
   1. Click Attach task.
   2. Find and locate the required task by clicking the search icon (![Search icon]()).
   3. Add the task as a release task by clicking the task number.
   {#t_ScopeARelease__substeps_hnf_r12_fmb}
5. Click Submit.

*[\>]: and then