Create a release for a product or service
- UpdatedJul 31, 2025
- 3 minutes to read
- Zurich
- DevOps
Create a product or service release when all planned product enhancements and product features are ready.
Before you begin
- Define release scope using product enhancements
- Complete the release planning by moving enhancements into different releases
Role required: sn_dpr_model.product_manager
About this task
Releases can follow a timeline-oriented and stage-oriented release process. For more information, see Release for a product or service.
For creating a release for multiple products using the wizard, see Create a release with a wizard.
Procedure
Result
- A release is created in the Draft or Pending state based on the following conditions:
- If all fields on the form are filled, the release is created in the Pending state and opens in the Release Dashboard page.
- If either the Release template or Release readiness target fields, or both, are empty, the release is created in the Draft state.
You can finish creating the release later from the Release Planning page or from the Releases list.
- If you have selected a timeline-oriented release template, then the following options might apply as defined in the template:
- If available, the schedule from the template is applied to the release. The actual working days for the phase and release are calculated by considering the holidays and weekends in the schedule.
When considering the holidays for calculating phase or release durations, a release is not created if:
- The start date of the release or its phase falls in the past.
- The duration exceeds the max duration defined in the system property.
In that case, you have to select another schedule or adjust the holidays. For more information, see Holiday schedules in a release.
- Any key dates from the template are added to the release. The date of each key date is calculated using the number of days from the start or end of the phase specified in the release template.Note: If the release has a holiday schedule and a key date from the template falls on a holiday, the last workday before or after the holiday is considered as the revised key date.
- If available, the schedule from the template is applied to the release. The actual working days for the phase and release are calculated by considering the holidays and weekends in the schedule.
When considering the holidays for calculating phase or release durations, a release is not created if:
- If an out-of-band release is created on a date that already has a release target, it uses that release target. However, if there’s no release target for that date, one is created, when the system property sn_dpr.out_of_band_release_allowed is set to true. The release admin for this new release target is the same as the one for the selected release calendar.
- Any artifacts associated with the product or release are added to the release. For more information, see View and manage data from external tools.
You can add or remove artifacts from a release as needed. For more information, see Manage artifacts in a release.