Dataset: Commits from pull requests
Entity: Commit
Field ID: id
Type: Datetime
Description: The ID assigned to the record by the source application.
Source: App
From: |
|
Github (Commits) |
|
Gitlab (Commits) |
|
Bitbucket (Commits) |
|
Azure DevOps (Commits) |
|
Jira | N/A |
ClickUp | N/A |
Trello | N/A |
Reporting Use Cases
The ID (Source) field provides the unique SHA hash for a commit from its source Git platform. Its primary role in reporting is to enable meaningful drilldowns from aggregated metrics to the specific, individual commits that make up the total.
Enabling Accurate Drilldowns: This is the most critical use case for this field. When you view a high-level metric, such as a bar chart showing "Commits per Day," and you click on a bar representing "15 commits," you need a way to see exactly which 15 commits those are. The drilldown view that appears will be a list of those individual commits, and the
ID (Source)serves as the unique key for each record. This allows you to see the specific SHA for every single commit, providing a direct, unambiguous reference that you can use to investigate the code in your Git tool.Context in List Reports: In any list-based report that displays individual commits (not just drilldowns), the
ID (Source)(often shortened for readability) should be included as a dimension. It serves as the primary unique identifier, giving context and allowing for easy cross-referencing with your source code repository.Direct Filtering: While less common for general reporting, you can also use this field for direct filtering if you have a specific commit SHA you need to investigate. A filter like
ID (Source) = "a1b2c3d4e5f6a7b8c9d0..."will isolate that single commit for detailed analysis.