Skip to main content

Reviews > ID (source)

Tom Williams avatar
Written by Tom Williams
Updated yesterday

Dataset: Reviews from pull requests

Entity: Pull Request Review

Field ID: id (source)

Type: Text

Description: The ID assigned to the record by the source application.

Source: App

From:

Github (PRs)

id

Gitlab (MRs)

Generated using the merge request ID, the author type, and the author ID.

Bitbucket (PRs)

Generated using a SHA256 of the review content

Azure DevOps (PR Threads)

Generated using the thread ID and the comment ID.

Jira

N/A

ClickUp

N/A

Trello

N/A

Reporting Use Cases

The ID (Source) field from the Reviews dataset provides the unique identifier for a review as it appears in the source application (e.g., GitHub). Its primary role in reporting is to serve as a direct reference, enabling precise drilldowns and ensuring each review can be uniquely identified in detailed lists.

  • Enabling Accurate Drilldowns: This is the field's most critical function for analysis. When you create an aggregated widget, such as a chart of "Reviews Performed per Week," and click on a data point representing "20 reviews," the ID (Source) is the key that allows the system to fetch and display the 20 individual reviews that make up that total. It provides an unambiguous reference for each review in the detailed list.

  • Context in List Reports: In any report that lists individual reviews, including the ID (Source) as a dimension provides essential context. It allows for easy cross-referencing with the source tool, which is invaluable for auditing or for digging into the specifics of a particular piece of feedback.

  • Filtering for Specific Reviews: While less common, if you know the exact ID of a specific review you need to investigate, you can use a direct filter to isolate it.

    • For example, you could create a report with a filter like ID (Source) = "12345678" to pull up the details of a single, specific review.

Did this answer your question?