Overview

The Release Management feature for Applications and Integrated Applications is a core capability for modular delivery and system integration. It allows delivery units under a Product to be defined as Applications, so each Application can have its own version management, build process, and release lifecycle. This supports more precise management, faster iteration, and better traceability.

At the same time, Integrated Applications make it possible to combine multiple Applications into a single release unit. This is especially useful for system integration, customized delivery, and multi-project delivery scenarios, helping organizations improve responsiveness and delivery efficiency in large-scale release management, agile iteration, and customer-specific delivery.

Use Cases

• Modular delivery: In large Products, multiple modules with different responsibilities can make release coordination difficult if ownership boundaries are unclear. By defining modules as independent Applications, each Application can follow its own release rhythm and ownership model, making release planning more controllable and collaboration more efficient.
• Customer-specific delivery or system integration delivery: In multi-customer or system integration scenarios, teams often need to combine existing capabilities into different delivery packages. With Integrated Applications, multiple Applications can be combined flexibly for version management and release, supporting customer-specific delivery or full-system delivery while improving responsiveness and productization capability.
• Release traceability and closed-loop management: If Requirements, Bugs, and Builds involved in a release are not managed together, release content can become unclear and issues become hard to trace. This feature links Versions with Requirements, Bugs, and Builds, creating a closed loop for issue analysis, change traceability, and risk control.
• Cross-team delivery coordination: In environments with parallel versions and rapid iteration, product teams need key checkpoints to align teams and communicate priorities. This feature supports milestone releases, which are clearly marked in the release list and roadmap, helping teams focus on key goals and align product planning with release cadence.

I. Application Management

Applications and Integrated Applications

For example, when a product version is prepared for external release, users may see it as a single version release. Internally, however, that release may actually consist of multiple deliverables, such as:

• an all-in-one installation package
• a Linux environment package
• a desktop client

Each of these deliverables can be shipped independently, which is important for modular delivery.

With the Applications feature, each of these deliverables can be defined as an Application. Then, through the Integrated Application release model, multiple Applications can be combined into one integrated release for external delivery, making release management more structured and easier to trace later.

When issues need to be investigated afterward, teams can trace them back through the integrated release and identify the versions of the individual Applications included in it.

II. Product (Application) Releases

After the Requirements in a Product Plan have been completed by the project team and passed testing, the product manager performs final acceptance. In Requirements, the stage is manually changed to Accepted, and then the Product is released to create a delivery record.

Go to Product > Releases and click Create Release to create a release record.

Link the implemented Requirements and resolved Bugs, and then create the release.

1. Create a Release

Click Releases > Create Release.

图1

Select the Application to be released, enter the Application Version, and choose the Build to release. By default, the system links completed Development Requirements and resolved Bugs from the selected Build to the Release.

You can also set whether this Release is a Milestone. If enabled, a milestone marker appears in the release list and roadmap.

2. Link Requirements and resolved Bugs

After the Release is created and saved, the system opens the Release details page. There, you can link completed Requirements, resolved Bugs, and remaining Bugs for this Release.

图2

If the linked Build contains artifacts, those artifacts are also linked to the Release by default. They can be removed if they are not needed for this Release.

图3

III. Multi-Application (Integrated Application) Releases

To create an integrated release across multiple Applications, follow these steps:

1. Create a separate Application for each deliverable to be released

Go to Product > Releases, click Manage Applications in the upper-right corner, and then click Create Application.

When creating an individual Application, set Integrated Application to No, then enter the Application name and create it. Repeat this step until all Applications that will be included in the integrated release have been created.

2. Create an Integrated Application

Click Create Application again, set Integrated Application to Yes, and select all individual Applications to be included. The created Integrated Application will display an integration label.

图4

图5

3. Release an individual Application

Go to Product > Releases and click Create Release.

When releasing an individual Application, select the previously created standalone Application in the Application field, then enter the Application version.

Because an individual Application may be released multiple times, it may have multiple version numbers. When creating an integrated release later, you can choose the specific versions you want to include.

图6

4. Release an Integrated Application

After the individual Applications have been released, you can create the Integrated Application release.

Go to Product > Releases and click Create Release again.

When releasing an Integrated Application, select the previously created Integrated Application in the Application field, then specify the released version number for each included Application.

After the Integrated Application is released, the Requirements, Bugs, and artifacts from those included releases are synchronized to the Integrated Application release.

图7

图8

IV. Release Management

1. Edit or delete a Release

On the Release details page, you can edit or delete the Release, and you can also add a log entry for it.

图9

2. Release status management

For a Release that has not started, you can click Release to proceed. During this action, you must specify whether the Release is Successful or Failed. If the Release succeeds, its status changes to Released. If it fails, its status changes to Release Failed.

图10

3. Stop maintaining a Release

After a Release has been published, you can mark that version as No Longer Maintained. Its status then changes accordingly.

图11