Skip to main content
Version: Release 24.1

Configure Progression Boards

release-pro-label-only

Learn how to configure your Delivery Insights progression board and track your packages.

Configure the Digital.ai Release Dashboard

  1. From the left-navigation pane, click Dashboards > + Add custom dashboard.

  2. Hover over the Delivery Insights Dashboard card and click Select.

    add-dashboard

  3. Type a name and description for the dashboard (Pet Clinic Dashboard in this example) and click Create.

    add-dashboard

    The new dashboard (Pet Clinic Dashboard in this example) is created.

    add-dashboard

  4. Click Configure dashboard.

  5. Hover over the progression board splash screen and click the Configure icon. The Edit tile pane shows up.

    add-dashboard

  6. Select the Delivery Insights server from the Insights Service drop-down list.

  7. Click Create new progression and type a name for your progression (Pet Clinic Web Server in this example) and click Save. This gets automatically updated in the Progression field.

    add-dashboard

  8. Type a meaningful title (Pet Clinic Package Progression in this example) for the progression in the Title field.

    add-dashboard

  9. Click Save.

    The new Progression Board is created.

    add-dashboard

  10. Click Back to view mode.

Add Your Value Stream Phases

  1. Click Add Phase.

  2. Click the + icon on the sides of the phases. You can add as many phases as you want.

    add-phases

  3. Type a name for all the phases you add.

    add-phases

  4. Click Save. The phases are added to the Progression Board.

    add-phases

Add an Application

  1. Click Add application. The Add application pane shows up.

  2. Type a name for the application (Web Server in this example) in the Application name field.

  3. Select a source control (GitHub in this example) from the Source Control drop-down list.

  4. Select your GitHub server from the Server name drop-down list (GitHub-delivery-insights-demo-docs in this example).

  5. Select your GitHub repository from the Repository name drop-down list (Delivery-insights-repo in this example).

  6. Select a ticketing system (JIRA in this example) from the Ticketing System drop-down list.

  7. Select the Jira server (JIRA-server in this example) from the Server name drop-down list.

    add-apps

  8. Scroll down and click Save.

    The new application (Web Server) is created in the Progression Board.

    add-apps

How to Recover The Payload Url of an Application?

  1. Go to the Progression Board and click the application's name. The Application Details pane appears. recover-webhook-url
  2. Click the webhook icon webhook-icon in the Source Control section. The Configure WebHook dialog appears. recover-webhook-url
  3. Click the Copy to clipboard icon to copy the Payload URL. Now, click OK to close the dialog box.

Configure the Application's Webhook in Github

  1. Log in to GitHub.

  2. Select your repository.

  3. Select the Settings tab.

  4. Select Webhooks from the left pane.

  5. Click Add webhook.

    webhooks

  6. Copy and paste the application's Payload URL into the Payload URL text box.

  7. Select application/json from the Content type drop-down list.

  8. Leave the defaults for the other fields and click Add webhook.

    webhooks

You are now all set with the configuration.

Example

Let us now push some commits to the GitHub repository, create a package in the progression board, promote a package revision from one phase to the other, and finally remove (deliver) the package revision from the progression board.

For this tutorial, I have created three Jira work items as illustrated in the following image to commit my changes in the GitHub repository. Note the Jira work item IDs (ENG-5580, ENG-5581, ENG-5582), which I would include in the commit messages for creating association between the commits and work items.

jira tickets

Here's an example commit message to illustrate how to include the Jira work item ID in the commit message.

jira commit message example

Go on and push your commits to your repository. When you have enough commits, you can create a package to track the work items/commits.