Project Settings
1. Introduction of Sanplex features
1.1. Core Management Framework
1.1.1 Program
1.1.2 Project
1.1.3 Product
1.1.4 Execution
1.1.5 Management Models
1.2. Dashboard
1.2.1 Getting Started with Tutorials
1.2.2 Quick Add
1.2.3 Notification Center
1.2.4 Effort Tracking
1.2.5 Dashboard - Project and Execution
1.2.6 Dashboard - My Work, Contribution, and Recents
1.2.7 Dashboard - Approval
1.2.8 Contacts
1.3. Program
1.3.1 Program List
1.3.2 Program Kanban
1.3.3 Create Program
1.3.4 Create Sub-Programs
1.3.5 Project Charter Management
1.4. Product
1.4.1 Create Product
1.4.2 Manage Modules
1.4.3 Multi-Branch and Multi-Platform Management
1.4.4 Manage Plans
1.4.5 Manage Requirements
1.4.6 Requirement Reviews
1.4.7 Requirement Status and Phase
1.4.8 Create Releases
1.4.9 Track Progress
1.4.10 Business Requirements and Multi-Level Requirements
1.5. Project
1.5.1 Scrum Project
1.5.2. Waterfall Project
1.5.2.1 Manage Project Phases
1.5.2.2 Project Design
1.5.2.3 Project Matrix
1.5.2.4 Project Reports and Earned Value Management
1.5.2.5 Project Baselines
1.5.2.6 Project Change
1.5.3. Kanban Project
1.5.3.1 Set Up Kanban Projects
1.5.3.2 Configure Kanban Boards
1.5.3.3 Use Kanban Boards
1.5.4 Hybrid Agile Project
1.5.5 Hybrid Waterfall Project
1.5.6. Project Settings
1.5.6.1 Project Setup
1.5.6.2 Project Executions
1.5.6.3 Project Requirements
1.5.6.4 Project Builds
1.5.6.5 Project Tests
1.5.6.6 Project Docs
1.5.6.7 Project Releases
1.6. Admin Settings
1.7. Workflow

Project Releases

2026-03-28 19:52:47
Sanplex Content
447
Last edited by Jing WANG on 2026-08-31 18:29:28
Share links
Summary: Learn how to create applications and releases, associate builds, manage Stories and Bugs, publish releases, record effort, and terminate releases.

Catalog

A project can create releases directly, and those releases are also synced to the release list of the linked product.

After testing is completed for a specific project build, you can create a release for the corresponding application version and publish it when it is ready.

The following example uses a Scrum project to explain the project release workflow.

I. Create an Application

Before creating a release, create an Application under the associated product.

Go to Product > Select a Product > Release, and click Manage Application. On the application list page, click Create Application in the upper-right corner.

The Product Release application list showing existing applications and the Create Application button used to add a new application for the selected product.

When creating an application, you can choose whether it is an Integrated Application.

For an Integrated Application, select the applications to include. An Integrated Application can be used to group multiple applications into a combined deliverable.

The Create Application dialog showing the Integrated Application option, Application name, Included Applications, and Description fields for creating a standard or integrated application.

Click Save to create the application.

II. Create a Release

Go to Release and click Create Release.

The Product Release page showing the release list, status filters, Manage Application button, and Create Release button for adding a new application release.

On the Create Release page, select the application, enter the Application Version, and set the Planned Release Date.

You can also:

  • select one or more builds under Include Build
  • mark the release as a Milestone
  • link completed Stories and fixed Bugs from the selected build to the release
  • enter a description
  • specify mail recipients
  • attach files The Create Release page showing Application, Application Version, Include Build, Release Status, Planned Release Date, milestone, description, mail recipient, and file attachment settings.

Use Include Build to select the build or builds associated with the release. When Link completed stories and fixed bugs from the build to the release is selected, the corresponding completed Stories and fixed Bugs are linked to the release.

The Create Release page with the Include Build dropdown open, showing available builds that can be selected and linked to the current application release.

Click Save to create the release.

III. Manage Stories and Bugs in a Release

After the release is created, open its details page.

The release details include the following tabs:

  • Completed Story
  • Fixed Bug
  • Active Bug
  • Basic Info

You can review the Stories and Bugs associated with the release, use Link Story or the corresponding Bug linking actions to add items, and use available search conditions to locate records as needed.

The release details page showing Completed Story, Fixed Bug, Active Bug, and Basic Info tabs, together with actions for linking Stories and managing release information.

IV. Manage a Release

On the release details page, you can use the available actions to manage the release.

These actions include:

  • Effort — record effort for the release
  • Edit — update release information
  • Delete — delete the release
  • Terminate — terminate the release when applicable

The release details page showing the Effort, Terminate, Edit, and Delete actions available for managing the selected release.

V. Publish a Release

When the release is ready, click Publish.

In the Publish dialog, select the release result:

  • Released
  • Release Failed

Enter the Actual Release Date, add notes if needed, and click Publish.

The Publish dialog showing Released and Release Failed status options, the Actual Release Date field, a Note editor, and the Publish button.

After publication, the release status is updated accordingly in the release list.

VI. Terminate a Release

For a released version that should be terminated, click Terminate.

The system displays a confirmation dialog. Click Confirm to terminate the release.

The release termination confirmation dialog asking the user to confirm termination of the selected release, with Confirm and Cancel buttons.

Write a Comment
Comment will be posted after it is reviewed.