By specifying a Ticket ID pattern, individual commits can be linked to tickets, allowing for measuring Change Coupling Across Commits and Code Churn by Tasks.

If PM Data Integration is enabled, the pattern used for matching will be created automatically to extract ticket IDs matching the configured integration. In the image below, you can see that this page is editable as there is no PM integration configured for that project:

If project keys on commits differ from PM data project keys, at PM integration configuration, you can use Project Aliases - A mapping from project aliases used on commits to PM data projects.

More in Project Management (PM) Integration

What is Considered Unplanned Work?How to Handle a Timeout Error During PM Analyses?What to Do When the Ticket ID Pattern Does Not Match Jira Tickets?Why Are No Issues Fetched After Setting Up the PM Integration in Azure DevOps?

What Does the 'Map Commit to Pull Requests Issues' Option Do?Previous Which Information is Retrieved from Jira When PM Integration Is Enabled?Next

Still need help? Ask the team

Cloud Docs
On-Prem Docs