How to Track Jira Issues and GitHub Commit History in Digital Product Release Workspace

Suhyeon Lee
Tera Expert

We have configured the product for DPR usage and connected Jira and GitHub.
What needs to be done to ensure that the commit history linked to issues in Jira is also tracked in DPR?

Seeing that a Commits tab exists, it seems that the related information should be collected.
However, it is not being collected.

Please help!

 

 

SuhyeonLee_0-1759198886920.png

 

SuhyeonLee_2-1759198985114.png

 

 

1 ACCEPTED SOLUTION

@Suhyeon Lee , As per your screenshot, I noticed that you are providing Workitem number of DevOps instead provide your native id.

Please update it to the following format:

KTDSPOC-134: {your message}

Also, ensure that both your plan and repo are set to track=true.

View solution in original post

5 REPLIES 5

SuryakiranMeka
ServiceNow Employee
ServiceNow Employee

Hi ,@Suhyeon Lee 

To include commit information in your JIRA work items, please follow these steps:

  1. Associate the JIRA plan and GitHub repository with a product in DPR.
  2. When making a commit in GitHub, include the native ID of the JIRA work item in the commit message by following one of the patterns mentioned in the attached document link.
    Example: WORKITEM1: test commit
  3. This will automatically link the commit to the corresponding work item, allowing you to view commit details directly within the work item

For more information please follow this document:

https://www.servicenow.com/docs/bundle/zurich-it-service-management/page/product/enterprise-dev-ops/...

 Hi, @SuryakiranMeka 

 

The Jira project and GitHub repository are already connected to the product configured in DPR.
As you mentioned, I included the Work Item number in the commit message, but the linkage is not happening.
Is there something I might have missed?

 

SuhyeonLee_0-1759205761652.png

SuhyeonLee_1-1759205792998.png

 

@Suhyeon Lee , As per your screenshot, I noticed that you are providing Workitem number of DevOps instead provide your native id.

Please update it to the following format:

KTDSPOC-134: {your message}

Also, ensure that both your plan and repo are set to track=true.

@SuryakiranMekaThank you, you really saved my day!

 

SuhyeonLee_0-1759214775906.png