Version management

Updated at:

Alibaba Cloud DevOps Projex lets you use versions to plan product features and ensure on-time delivery. You can use versions in both projects and programs. In a project, you can add work items from the project to a version. In a program, you can add work items from associated projects to a program version.

Enable the version service

  1. In a project, navigate to Settings > Navigation Service to enable the version service. If the version service is not listed, you must first enable it in the project's template.

  2. In the template settings, add the version service under Service Management.

  3. After adding the service, return to Navigation Service and turn on the switch next to Version to enable the Version service.

Version creation

Navigate to Version > Version Management and create a new version. Fill in the following parameters:

Parameter

Type

Required

Version Name

Input box

Yes

Version Owner

Drop-down list

Yes

Start Date

Date picker

No

Release Date

Date picker

No

Then, click Create or Cancel at the bottom.

Version planning

You can add existing work items to a version. You can also create work items directly within a version.

Click Add Work Item in the upper-right corner. In the dialog box that appears, select the work items you want to add and click OK. When working in a program, you can select work items from any associated project.

Version overview

On the version overview page, you can view basic information, edit and view version announcements, associate test plans you participate in, and track version activities.

Basic information module: Displays the core metadata of the version, including the version owner (avatar), version status (In Progress), and the start and release dates.

Version announcement module: Describes the main updates in version V5.6.3, including new features such as user-configured switches in multiple availability zones and user-configured message notifications. It also highlights optimizations to Active Directory and LDAP user synchronization and asset authorization processes.

Test plan module: Lists the test plans for the version (1/1 pages). Each entry includes fields such as Plan Name, Admin, Plan Start Date, Plan End Date, Status, Pass Rate, Closed/Total Defects, and Actions. Two plans are listed: "[public cloud] Support icon settings for types" (Completed, 100% Pass Rate, 1/1 Defects) and "[public cloud] Configure field display in Gantt chart" (Completed, 100% Pass Rate, 0/0 Defects).

Version activities module: Displays a log of version-related activities in reverse chronological order, including "Created release notes", "Moved test plan [public cloud] Support icon settings for types into the version", and "Moved test plan [public cloud] Configure field display in Gantt chart into the version".

Release notes

Click the button in the upper-right corner to edit the release notes.

Version lock

After planning is complete, you can use an iteration lock to lock the version. This prevents changes to the delivery scope of the version.

Note

After a version is locked, you cannot move requirements or epics into or out of the version. However, users with version management permissions, such as project administrators and version owners, can bypass this restriction.

Program versions

  • When you unlink a program from a project, its associated program versions are not removed from work items. A prompt appears to guide you in manually deleting them.

  • When you delete a program, its associated program versions are not automatically removed from work items. You must delete these versions manually.