Dataset: Issues & Pull Requests
Entity: Pull Requests, Issues
Field ID: url
Type: Text
Description: The URL of the item in the source application
Source: App
Transformation logic: N/A
From: |
|
Github (PRs, Issues) |
|
Gitlab (PRs, Issues) |
|
Bitbucket (PRs) |
|
Azure DevOps (PRs, Issues) | Built from the host and record ID |
JIRA (Issues) | Generated using the Jira instance domain and the issue key |
ClickUp (Issues) |
|
Trello (Issues) |
|
Reporting Use Cases
The Url field's primary purpose is to provide a direct, clickable link from any widget back to the original item in the source application (e.g., GitHub or Jira). While not used for calculations, it is an indispensable element for context and can also be used for filtering.
Providing Direct Access in Reports: This is the most critical use case. In any list-based report or drilldown, including the
Urlfield as a dimension provides a direct link to the source item. This allows users to seamlessly navigate from a high-level report in Keypup to the detailed context of the issue or pull request with a single click.Filtering by Source Application: The URL's structure allows you to filter your reports to include or exclude items from specific platforms.
For example, to create a widget that only shows items 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 data separately. Note, however, that using theSource Appfield is generally a better alternative for this use case.
Custom Formulas for Advanced Extraction: While other fields are often more direct, you can use custom formulas to parse the URL and extract specific information that might not be available otherwise.
For instance, you could extract the GitHub organization name from the URL with a formula like
SPLIT(url, "/")[3]to group work by the owning organization.