Manage Application Versions on the Stages Board

The stages board provides a visual representation of the versions that exist for the selected application and their current location in your lifecycle. Use the stages board to promote application versions between stages and to access detailed information about a specific version, its associated evidence, and possible security risks.

To access the stages board:

In the Platform module, select AppTrust > Applications.
In the Applications table, click the name of the relevant application.
In the sidebar, click Lifecycle. The Stages Board tab is displayed by default.

Stages Board Layout

The board is divided into the stages that are defined as your project lifecycle (see Edit the Lifecycle in the Platform UI). The final stage, which is the release stage for your application version, is called PROD and cannot be modified. The total number of versions on display appears above the board.

Policy Gates

If lifecycle policies have been defined, they appear in gray boxes next to the title of each stage. Lifecycle policies control the movement of application versions between stages by defining a set of rules that must be adhered to before the version is allowed to proceed to the next stage.

It is up to the administrator to decide which stages have policies attached to them and whether versions that violate the rules defined by the policy are allowed to proceed with a warning or fail.

Each user-defined stage can have up to 2 gates with policies:

Entry gate policies determine whether an application version is allowed to be promoted to the stage. This gate is represented by a gray box to the left of the stage title.
Exit gate policies determine whether an application version is allowed to be promoted out of the stage. This gate is represented by a gray box to the right of the stage title.

📘
Note
Stages and the order in which they appear in the lifecycle are defined by an administrator in the Stages & Lifecycle page.
The default release stage, PROD, can contain a single gate called Release.

Click the gray box to view the policies currently assigned to that gate. You can see the rules defined for the policy as well as the action taken in case of a violation (Warning or Fail).

✅
Tip
Click Create Policy to add a policy to the gate. For more information, see Create Lifecycle Policies.

Application Version Cards

Application versions appear in the Unassigned category initially after they are created. The card for each version contains the version number, the latest promotion performed on the version, and the date & time when the version was created/promoted.

As the application version is promoted to other stages, its card moves under the relevant stage. Icons indicate which type of promotion was performed (copy artifacts or move artifacts):

In the example shown above, cards for various versions of the Pizza Shop application are displayed. As can be seen, each version is located in a different stage, each of which represents a distinct phase in the SDLC. In this example, version 4.2.0 has been promoted to the QA stage while version 4.1.5 has been promoted to PROD as a trusted release. An application version can appear in only one stage at a time.

Failed promotions are marked with an error banner, as shown below.

Banners are also used to show operations in progress, such as application version creation or promotion.

Filtering the Stages Board

There are several tools available for filtering the application versions displayed on the stages board:

Filter by time: Use the dropdown list to limit the board to application versions created over the past 7 days, 30 days, or 90 days. You can also configure a custom time filter or view all versions. The default value is Any Time.
Search window: Use the search window to filter the stages board according to version or version tag . For example, if all your release candidates are tagged release-candidate, you can filter the stages board to display only those application versions.