Dataset: Issues & Pull Requests
Entity: Pull Requests, Issues
Field ID: _system_id
Type: Text
Description: The universal ID assigned to the record to uniquely identify it across all application records.
Source: Calculated
Transformation logic: Generated using the Record ID and the Project ID to create a truly unique ID.
From: |
|
Github (PRs, Issues) | Calculated |
Gitlab (PRs, Issues) | Calculated |
Bitbucket (PRs) | Calculated |
Azure DevOps (PRs, Issues) | Calculated |
Jira (Issues) | Calculated |
ClickUp (Issues) | Calculated |
Trello (Issues) | Calculated |
Reporting Use Cases
The ID (system) field is a unique identifier assigned by Keypup to every item, ensuring that each issue and pull request has a distinct ID, even across different projects or applications. Its primary role in reporting is to provide a reliable basis for accurate counting and aggregation.
Counting Distinct Items Across Datasets: This field is especially powerful when you need to count unique parent items from a related dataset like Comments or Reviews.
To find the number of unique pull requests that received comments, you would use the Comments from Issues/PRs/Reviews dataset and a metric with the formula
COUNT_DISTINCT(parent_system_id). This correctly counts each pull request only once, no matter how many comments it has.
Ensuring Accuracy Across Projects: Unlike the
ID (source), which can be the same for different items in different repositories (e.g., PR #101 in Project A and PR #101 in Project B), theID (system)is always unique. This makes it the most reliable field for any aggregation that requires a distinct count of items across your entire organization.