Keypup

Dataset: Reviews from pull requests

Description: The URL of the review in the source application.

The <code>Url</code> field from the Reviews dataset provides a direct, clickable link to a specific review in its source application. Its most critical function is to bridge the gap between high-level reporting and the detailed, actionable context of the original feedback.

Enabling Drilldowns and Investigation: This is the field's most essential use. When you create an aggregated widget, such as a chart of "Reviews per State," and drill down into a specific slice like <code>CHANGES_REQUESTED</code> the <code>Url</code> field is a mandatory dimension in the resulting list. It allows users to instantly navigate from the aggregated data to the exact review that needs attention.

Providing Context in Lists: In any report that lists individual reviews, including the <code>Url</code> as a dimension transforms a static report into an actionable tool, enabling users to read the full context, see the associated code, and participate in the discussion directly in the source application.

Filtering by Source Platform: You can also use the URL's structure to filter your reports by the source platform. For example, a filter like <code>Url ~ "github.com"</code> will create a widget that only shows reviews from your GitHub repositories, allowing you to analyze activity on a per-platform basis. Note, however, that using the <code>Source App</code> field is generally a better alternative for this use case.

- Enabling Drilldowns and Investigation: This is the field's most essential use. When you create an aggregated widget, such as a chart of "Reviews per State," and drill down into a specific slice like <code>CHANGES_REQUESTED</code> the <code>Url</code> field is a mandatory dimension in the resulting list. It allows users to instantly navigate from the aggregated data to the exact review that needs attention.
- Providing Context in Lists: In any report that lists individual reviews, including the <code>Url</code> as a dimension transforms a static report into an actionable tool, enabling users to read the full context, see the associated code, and participate in the discussion directly in the source application.
- Filtering by Source Platform: You can also use the URL's structure to filter your reports by the source platform. For example, a filter like <code>Url ~ "github.com"</code> will create a widget that only shows reviews from your GitHub repositories, allowing you to analyze activity on a per-platform basis. Note, however, that using the <code>Source App</code> field is generally a better alternative for this use case.

Reviews > URL

Find answers and get help from Intercom Support and Community Experts

This site employs cookies and other technologies that we and our third party vendors use to monitor and record personal information about you and your interactions with the site (including content viewed, cursor movements, screen recordings, and chat contents) for the purposes described in our Cookie Policy. By continuing to visit our site, you agree to our {websiteTermsLink}, {privacyPolicyLink} and {cookiePolicyLink}.

This site uses cookies and similar technologies ("cookies") as strictly necessary for site operation. We and our partners also would like to set additional cookies to enable site performance analytics, functionality, advertising and social media features. See our {cookiePolicyLink} for details. You can change your cookie preferences in our Cookie Settings.

We use cookies to make our site work and also for analytics and advertising purposes. You can enable or disable optional cookies as desired. See our {cookiePolicyLink} for more details.

Advertising cookies are set by our advertising partners to collect information about your use of the site, our communications, and other online services over time and with different browsers and devices. They use this information to show you ads online that they think will interest you and measure the ads' performance. Social media cookies are set by social media platforms to enable you to share content on those platforms, and are capable of tracking information about your activity across other online services for use as described in their privacy policies.

These cookies enable the website to provide enhanced functionality and personalisation. They may be set by us or by third party providers whose services we have added to our pages. If you do not allow these cookies then some or all of these services may not function properly.

These cookies are necessary for the website to function and cannot be switched off in our systems.

These cookies allow us to count visits and traffic sources so we can measure and improve the performance of our site. They help us to know which pages are the most and least popular and see how visitors move around the site.

You have the right to opt out of the sale of your personal information. See our {cookiePolicyLink} for more details about how we use your data.

Your Privacy Choices

We use cookies to enhance your experience. You can customize your cookie preferences below. See our {cookiePolicyLink} for more details.

Cookie Settings

Link, Press control-option-right-arrow to exit

Empty Help Center

Uh oh. That page doesn’t exist.

Disappointed

Neutral

Smiley

Thinking...

Searching through sources...

Analyzing...

Tickets submitted through the messenger or by a support agent in your conversation will appear here.

From:
Github (Reviews)	`url`
Gitlab (MRs)	`merge_request.web_url`
Bitbucket (PRs)	`pull_request.links.html.href`
Azure DevOps (PR Threads)	The parent PR URL
Jira	N/A
ClickUp	N/A
Trello	N/A

Reviews > URL

Reporting Use Cases