Dataset: Comments
Entity: Comments
Field ID: url
Type: Text
Description: The URL of the comment in the source application
Source: App
Transformation logic: N/A
App Mapping
Github (Comments) |
|
Gitlab (Comments) | Calculated: link to the comment on its parent issue or merge request ( |
Bitbucket (Comments) |
|
Azure DevOps (Comments) | Calculated: URL of the parent issue or pull request |
Jira (Comments) | Calculated: URL of the parent issue |
ClickUp (Comments) | Calculated: link to the comment on its parent task ( |
Trello (Comments) | Calculated: URL of the parent card followed by |
Reporting Use Cases
The Url field from the Comments dataset provides a direct, clickable link to a specific comment in its source application (e.g., GitHub, Jira). Its primary and most critical function is to provide direct access and context in any report that lists individual comments.
Providing Direct Access in Drilldowns: This is the most essential use case. When you create a high-level widget, such as a chart of "Comments per Day," and then drill down into a specific day, the drilldown report should include the Url field as a dimension. This transforms the report into an actionable list, allowing users to click on any comment and be taken directly to the conversation in its original context.
Context in Comment Feeds: For any report that functions as an activity or comment feed, including the Url as a dimension is crucial. It provides the necessary link for users to not only read the comment but also to reply or react to it in the source tool.
Filtering by Source Application: The URL's structure allows you to filter your reports to include or exclude comments from specific platforms.
For example, to create a widget that only shows comments from GitHub, you can use a filter like
Url ~ "github.com". This is particularly useful if you have multiple tools connected and want to analyze their communication patterns separately. Note, however, that using theSource Appfield is generally a better alternative for this use case.