Dataset: Issues & Pull Requests
Entity: Pull Requests, Issues
Field ID: id
Type: Text
Description: The ID assigned to the record by the source app. Unique across all records from the same app.
Source: App
Transformation logic: N/A
From: |
|
Github (PRs, Issues) |
|
Gitlab (PRs, Issues) |
|
Bitbucket (PRs) |
|
Azure DevOps (PRs, Issues) | PRs: |
JIRA (Issues) |
|
ClickUp (Issues) |
|
Trello (Issues) |
|
Reporting Use Cases
The ID (source) field provides the familiar, human-readable identifier for an issue or pull request as seen in the source application (e.g., the pull request number in GitHub or the issue ID in Jira). Its primary use in reporting is for pinpointing specific items and providing essential context in lists.
Filtering for Specific Items: This is the most direct way to investigate a single work item. If you know the specific ID of the item you are looking for, you can create a report that targets it exclusively.
For example, to view the details of a single pull request, you can apply a filter like
ID (source) = "12345".
Providing Context in Reports: While not typically used for aggregation, id (source) is a fundamental dimension to include in any list-based widget.
When you create a table of issues or pull requests, adding
ID (source)as a dimension ensures that each item is clearly identifiable by the number that your team uses in their daily work, making the report intuitive and easy to cross-reference with the source tool.
Custom Formulas for Enhanced Identifiers: You can use this field in custom formulas to create more descriptive or unique references, especially when reporting on multiple projects at once.
For example, you can create a custom dimension that combines the project name with the source ID using a formula like
CONCAT(project_name, "#", id). This would generate a unique identifier like "my-project#12345" for each item, which can be very useful in complex reports.