Keypup

Dataset: Issues &amp; Pull Requests

Field ID: <code>base_ref_repository</code>

Description: The repository of the base ref (destination repository).

The <code>Base Ref Repository</code> field is essential for tracking and comparing development activities across your entire software portfolio. As a text field, it serves as a powerful tool for filtering your widgets to specific projects and as a primary dimension for cross-repository analysis.

Filtering and Scoping: You can create focused reports by including or excluding specific repositories.

- Project-Specific Dashboards: Build dashboards that only show data for a single codebase by applying a filter such as <code>Base Ref Repository = "my-main-application"</code>.
- Microservice Analysis: If you use a consistent naming convention, you can analyze a group of related services using a regex filter like <code>Base Ref Repository ~ "-service$"</code>.
- Excluding Legacy Code: To focus on active development, you can exclude older or less relevant projects with a filter like <code>Base Ref Repository != "deprecated-legacy-app"</code>.

Reporting and Comparison: Using <code>Base Ref Repository</code> as a dimension is the primary way to compare performance and activity across different projects.

- Activity Hotspots: A bar chart with <code>Base Ref Repository</code> as the dimension and <code>COUNT()</code> as the metric will quickly reveal which repositories have the most pull request activity.
- Performance Benchmarking: You can compare key DORA metrics across your portfolio. For instance, create a list widget with <code>Base Ref Repository</code> as the dimension and the average cycle time <code>AVG(merged_at - created_at)</code> as a metric to identify which projects have the fastest delivery pipelines.

Custom Formulas for High-Level Grouping: When you have many repositories, it can be useful to group them into higher-level categories for simplified reporting.

- For example, you can create a dimension that categorizes repositories by product line using a custom formula like <code>IF(base_ref_repository ~ '^(mobile|ios|android)', 'Mobile Apps', 'Web Apps')</code>. This allows you to roll up metrics and understand performance at a team or portfolio level rather than just a project level.

- Filtering and Scoping: You can create focused reports by including or excluding specific repositories.
 - Project-Specific Dashboards: Build dashboards that only show data for a single codebase by applying a filter such as <code>Base Ref Repository = "my-main-application"</code>.
 - Microservice Analysis: If you use a consistent naming convention, you can analyze a group of related services using a regex filter like <code>Base Ref Repository ~ "-service$"</code>.
 - Excluding Legacy Code: To focus on active development, you can exclude older or less relevant projects with a filter like <code>Base Ref Repository != "deprecated-legacy-app"</code>.
- Reporting and Comparison: Using <code>Base Ref Repository</code> as a dimension is the primary way to compare performance and activity across different projects.
 - Activity Hotspots: A bar chart with <code>Base Ref Repository</code> as the dimension and <code>COUNT()</code> as the metric will quickly reveal which repositories have the most pull request activity.
 - Performance Benchmarking: You can compare key DORA metrics across your portfolio. For instance, create a list widget with <code>Base Ref Repository</code> as the dimension and the average cycle time <code>AVG(merged_at - created_at)</code> as a metric to identify which projects have the fastest delivery pipelines.
- Custom Formulas for High-Level Grouping: When you have many repositories, it can be useful to group them into higher-level categories for simplified reporting.
 - For example, you can create a dimension that categorizes repositories by product line using a custom formula like <code>IF(base_ref_repository ~ '^(mobile|ios|android)', 'Mobile Apps', 'Web Apps')</code>. This allows you to roll up metrics and understand performance at a team or portfolio level rather than just a project level.

Issues and PRs > Base ref | Repository

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 (PRs)	`base_repository.name_with_owner`
Gitlab (PRs)	`target.path_with_namespace`
Bitbucket (PRs)	`destination.repository.full_name`
Azure DevOps (PRs, Issues)	`repository`
JIRA	N/A
ClickUp	N/A
Trello	N/A

Issues and PRs > Base ref | Repository

Reporting Use Cases