Editing a Release

Owned by Kevin Pham (Deactivated)
Last updated: Jan 23, 2018

Description

In Zephyr Enterprise, projects consists of releases that assist in organizing your testing. By default, when a project is initially created, there will always be a default release. This default release is labeled as "Release 1.0". Users can edit releases within a project which includes the following fields and options that can be changed: Name and Description of release, the ability to Hide the release and Map an External Defect Project to the release, and the Start Date and End Date. To learn how to edit releases, please view the steps below.

Terminology

 Click to view more information on terminology regarding this page
TermDescription
ReleaseA release is an iteration or version of testing within a project. Releases can house requirements, test cases, and defects for a project.
NameA name given to specify the release.
DescriptionA written representation to help provide an explanation for the release.
HideA way to hide or suppress a specific release.
Map External Defect ProjectA way to map an external defect project from Jira to the release.
Start DateThe date that the release starts.
End DateThe date that the release ends.

Table of Contents

The steps below describe in detail the general process of adding, editing, deleting, and cloning a release within a project for Zephyr Enterprise. To view further instructions for each individual function, please click the links provided below. By clicking on a link, you will be redirected to the page with the steps corresponding to the function selected. 

Editing Releases

Prior to Editing a Release

Prior to editing a release, there must be an existing project that has been created in Zephyr Enterprise. The project must be selected and the user must have selected the manage release button explained in the Release Setup section.

Scenario: You are a testing manager that just created a project called "Mercury" and you are managing your releases within project Mercury. You currently have 2 releases in the system. As a testing manager, you want to make edits to an existing release in project Mercury. You will be editing "Release 2.0" and changing the Name, Start Date, and End Date.

If this is your first time editing a release, you might want to create and work in a test project that doesn't affect another project, and work out any issues you might have with editing a release before you work in a live project.



1. In 'Manage Release', simply click on any release in the table to begin making edits and changes to the selected release. (In our scenario, we'll be selecting "Release 2.0")

2. A release detail section will appear below and this is where you'll be making edits to the releases. (In our scenario, we'll be changing only the Name, Start Date, and End Date)

3. After clicking on the release in the table., make changes to the Name of the release, Start Date, and End Date for the release. (In our scenario, we'll use "Release 3.0" as the updated name of the release, the start date will be changed to January 24, 2018, and the end date will be changed to January 31, 2018.)

The other fields are optional that can be filled out. Optional fields are displayed below for further explanation:

  • Description - A written representation to help provide an explanation for the release.
  • Hide - A way to hide or suppress a specific release 
    • Hiding a release will not delete any data.
    • Hiding a release will cause the release to not appear in the project's release drop-down list.
    • Users are able to access test cases via the Global Tree in the Test Repository.
    • Users are able to access read-only execution statuses in the Test Execution section of Zephyr Enterprise.
  • Map External Defect Project - A way to map an external defect project from Jira to the release.


4. Simply click the "Save" button to finalize all the details of the release and the new release will be created.

5. You can immediately switch to the Edited Release and start using it right away.


Back to Top ^