Skip to main content

Comments > URL

Tom Williams avatar
Written by Tom Williams
Updated today

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

From:

Github (Comments)

url

Gitlab (Comments)

url

Bitbucket (Comments)

link

Azure DevOps (Comments)

The URL of the parent item (issue or PR)

JIRA (Comments)

Generated issue link (see Issue url field)

ClickUp (Comments)

url

Trello (Comments)

Generated link using parent issue URL and comment id.

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.

Did this answer your question?