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.6. Admin Settings
1.6.1 Confluence Data Import
1.7. Workflow

Project Builds

2026-08-25 23:43:02
Sanplex Content
374
Last edited by Jing WANG on 2026-08-25 23:45:46
Share links
Summary: Learn how to create and manage Builds, link completed Stories, review related bugs, create Integrated Builds, and submit Builds for testing through Test Requests.

Catalog

Feature Overview

After the development team completes a set of Stories or bug fixes, they can create a Build and submit it for testing.

Using builds in software configuration management helps define the scope of testing, improve collaboration between developers and testers, and manage testing and bug-fix activities across different builds.

After a Build is ready for testing, the team can submit a Test Request for the Build. The request can then be tracked under Test > Test Request, while related test results can be viewed under Test Report.

Use Cases

  • After the development team completes Stories or resolves bugs, Project Builds help define the scope of the corresponding testing activities.
  • Completed Stories, resolved bugs, and reported bugs associated with a Build provide testers with clear information about the Build content and testing scope.
  • Project teams can manage Builds associated with different Executions, Products, and Applications.
  • For integration testing, multiple existing Builds can be included in an Integrated Build to support broader verification across development stages.

I. Create a Build

1. Create a Build

After the development team completes Stories or resolves bugs, the corresponding source code version can be prepared in the source code repository.

In a project, go to Build and click Create Build.

Project Build page showing the existing Build list with Product, Application, Execution, Build Author, and Actions columns, and the Create Build button in the upper-right corner.

On the Create Build page, configure the Build information. Available fields include Integrated Build, Product, Application, Inclusive Build, Name, Build Author, and Build Date.

You can also provide an SCM Path, Download Address, and upload files related to the Build.

Create Build page with Integrated Build enabled and fields for Product, Application, Inclusive Build, Name, Build Author, Build Date, SCM Path, Download Address, and file upload.

After the Build is created, it appears in the Build list. The Actions column provides the available operations for each Build.

Project Build list showing three Builds with their Product, Application, Execution, Build Author, and available action icons in the Actions column.

2. Link Stories and View Bugs

Open a Build to view its related information. The Build details page organizes the content into four tabs:

  • Completed Story
  • Resolved Bugs
  • Reported Bugs
  • Basic Info

Under Completed Story, you can use the available filters to locate Stories associated with the Build.

Build details page with the Completed Story tab selected, showing search criteria for locating Stories and the other tabs for Resolved Bugs, Reported Bugs, and Basic Info.

Click Link Story to associate additional completed Stories with the Build. Linked Stories are displayed in the Completed Story list together with their priority, status, creator, estimate, and phase information.

Completed Story tab for a Build showing two linked Stories with their priority, review status, creator, estimate, and phase, together with the Link Story button.

The other Build tabs provide related bug information:

  • Resolved Bugs lists bugs associated with the Build as resolved bugs.
  • Reported Bugs lists bugs associated with the Build as reported bugs.
  • Basic Info displays the main configuration and descriptive information for the Build.

3. Manage Builds

The Actions column provides operations for managing individual Builds, including submitting a Test Request, editing Build information, deleting a Build, and other available Build actions.

Close-up of the Build Actions column showing the action icons available for each Build, including the Submit Test Request, bug-related, edit, and delete operations.

Click a Build name to open its details page. Under Basic Info, you can review information such as Product, Platform/Branch, Application, Name, Inclusive Build, Build Author, Build Date, SCM Path, Download Address, and Description.

Build details page with the Basic Info tab selected, displaying Product, Platform/Branch, Application, Build name, Inclusive Build, Build Author, Build Date, repository information, and description.

II. Create an Integrated Build

A standard Build can be associated with a specific Execution. On the Create Build page, set Integrated Build to No, and select the required Execution and other Build information.

Create Build page with Integrated Build set to No and the Execution dropdown expanded, showing available Build Verification Sprint executions for creating an Execution-specific Build.

To consolidate existing Builds for broader integration testing, set Integrated Build to Yes.

Select the Product and Application, then use Inclusive Build to include the Builds that form part of the Integrated Build. Complete the remaining Build information and save the Build.

Create Build page with Integrated Build set to Yes, showing fields for Product, Application, Inclusive Build, Name, Build Author, and Build Date for creating an Integrated Build.

The resulting Integrated Build can be managed in the same Build list and provides access to its Completed Story, Resolved Bugs, Reported Bugs, and Basic Info.

III. Submit a Build for Testing

After the Build information and related Stories are ready, submit the Build for testing by creating a Test Request.

In the Build list, click the Submit Test Request action for the required Build.

Project Build list with the Submit Test Request action highlighted in the Actions column for the selected Build, alongside the other available Build management actions.

On the Submit Request page, configure the testing information. The page provides fields including Product, Execution, Build, Type, Owner, Members, Start, End, Status, Test Report, Request Name, and Priority.

The selected Build is carried into the request so that the testing activity is associated with the correct Build.

Submit Request page showing the selected Product and Build together with Execution, Type, Owner, Members, date range, Status, Test Report, Request Name, and Priority fields.

After the request is created, go to Project > Test > Test Request to view it. The list displays information such as the request name, priority, Product, Build, Execution, and owner.

Project Test Request page showing a request associated with the Project Builds integration Build, with columns for Request Name, Priority, Product, Build, Execution, and Owner.

Related test reports can be viewed under Project > Test > Test Report. The report list displays the report title, associated Project or Execution, Test Request, creator, creation date, and available actions.

Project Test Report page showing a cross-platform regression report linked to the Project Builds Test Request, with Project or Execution, creator, created date, and action information.

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