Lesson 10: Visualizing the movement of dots in the value stream
You can learn about the functionality of Jira, GitHub, Jenkins, and DevOps Deploy in the value stream and visualize the movement of dots from the backlog to build stages within the value stream.
-
Perform the following steps to move the dot from Backlog stage
to In Progress stage in the value stream page:
- Log in to Jira account by using login credentials.
- In the kanban board, move the Jira issue (App 1) from the Backlog to In Progress.
-
Open the value stream page in Measure. The dot representing the Jira issue (App 1) is moved from the
Backlog stage to the In Progress
stage.
- Click the dot representing the Jira issue (App 1) to view the work history.
-
Perform the following steps to move the dot from In Progress
stage to In Review stage in the value stream page:
- Log in to Jira account by using login credentials.
- In the kanban board, move the Jira issue (App 1) from the Backlog to In Progress.
- Log in to GitHub account by using login credentials.
- Navigate to the desired repository, edit the file, and then click Commit
changes....
The Commit changes dialog is displayed.
- Select Create a new branch for this commit and start a pull
request, and then click Propose changes.
The Open a pull request page is displayed.
- Important: Type the Jira issue ID in the Add a
description field. For example, App 1.Note: You can also add comments followed by the Jira issue in the Add a description field. For example, App 1 update.
- Click Create pull request.
- Open the value stream page in Measure. The dot representing the Jira issue (App 1) is moved from the
In Progress stage to the In Review
stage and the pull request is linked to the Jira issue.

- Click the dot representing the Jira issue (App 1) to view the work history. You can view the commit history in the related item section.
-
Perform the following steps to move the dot from In Review stage
to Merged stage:
- In the kanban board, move the Jira issue (App 1) from the In Review to Done.
- In the GitHub repository, close the pull request that you have created in step 2.g.
-
Open the value stream page in Measure. The dot representing the Jira issue (App 1) is moved from the
In Review stage to the Merged
stage.
- Click the dot representing the Jira issue (App 1) to view the work history.
-
Perform the following steps to move the dot from Merged stage to
Build stage:
- Sign in to your Jenkins application with valid login credentials.
- Open the Build_input job that you have created in Lesson 7: Setting up the build jobs in Jenkins.
- Click Build with Parameters.
- In the build number field, enter the build number. For example, #60.
-
Open the value stream page in Measure. The dot representing the Jira issue (App 1) is moved from the
Merged stage to the Build stage.
- Click the Pipeline tab. You can see the build number under the Input stage.
-
Perform the following steps to create a snapshot in DevOps Deploy:
- Log in to DevOps Deploy.
- Click the Applications option, and then click the application that you have created for the tutorial. For example, PROJ_process.
- Click the Components option in APP2 application page.
-
Select the component from the list that you have created for the tutorials. For
example, PROJ_Comp1
The component versions are displayed.
- Select the component from the list that you have created for the tutorials. For example, PROJ_Comp1
-
Click the Import New Versions option.
The Import New Versions dialog is displayed.
- Enter the Jenkins build number in the Version Name field. For example, #60
- Click Save.
-
Perform the following steps to add the build URL for the component version:
- Click the imported component version from the Component Version list.
- Click Create.
The Create Link dialog is displayed.
- Type
build.urlin the Name field. - Type the latest URL in the URL field.
- Click Save.
-
Click the Applications option in the menu bar.
The applications are displayed.
- Select the PROJ_process application from the list, and then click Snapshots.
-
Click Create Snapshot.
The Create Snapshot dialog is displayed.
- Enter the Jenkins build number in the Name field. For example, #60.
-
Click Save.
The Snapshot page is displayed along with the Jenkins build number. For example, Snapshot: #60.
-
In the Component Version tab, click the
Add.. option.
The Add Version dialog is displayed.
-
Select the Jenkins build number in the By Version Lookup
list. For example, #60.
The Jenkins build number is added to the Versions list for the corresponding Component.
-
Perform the following steps to move the dot from Build stage to
DEV stage:
- Open the value stream page in Measure.
- Click the Pipeline tab.
- Click Deploy button in the DEV environment.
-
Select the applications and version that you want to deploy. For example,
#60.
Note: Ensure that the build number in Input and the version that you want to deploy in DEV stage is identical.
-
Click Deploy.
You can see the build number under the DEV environment when the deployment is successful.
-
Click the Value stream tab. The dot representing the Jira
issue (App 1) is moved from the Build stage to the
DEV stage.
-
Perform the following steps to move the dot from DEV stage to
QA stage:
- Open the value stream page in Measure.
- Click the Pipeline tab.
- Click Deploy button in the QA environment.
- Select the application and version that you want to deploy.
-
Click Deploy.
You can see the build number under the QA environment when the deployment is successful.
-
Click the Value stream tab. The dot representing the issue
Jira issue (App 1) is moved from the Build stage to the
QA stage.
-
Perform the following steps to move the dot from QA stage to
PROD stage:
- Click Deploy button in the PROD environment.
- Select the application and version that you want to deploy.
-
Click Deploy.
You can see the build number under the PROD environment when the deployment is successful.
-
Click the Value stream tab. The dot representing the Jira
issue (App 1) is moved from the Build stage to the
PROD stage.