Keypup

Dataset: Issues &amp; Pull Requests

Field ID: <code>base_ref_branch</code>

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

The <code>Base Ref Branch</code> field is essential for understanding your development workflow and tracking where code changes are being deployed. As a text field, it is primarily used for filtering reports and as a dimension to categorize your pull requests.

Filtering and Scoping: You can focus your insights on the streams of work that matter most by filtering on the destination branch.

- Production Deployments: Create reports that only include pull requests merged into your main production branch by using a filter like <code>Base Ref Branch = main</code>.
- Release Monitoring: Use a regex filter such as <code>Base Ref Branch ~ ^release- </code>to monitor all pull requests related to a specific release cycle.
- Excluding Hotfixes: If you want to analyze feature work separately, you can exclude urgent fixes with a filter like <code>Base Ref Branch !~ ^hotfix-</code>.

Reporting and Analysis: Using <code>Base Ref Branch</code> as a dimension allows you to compare different development streams.

- Activity per Branch: A bar chart with <code>Base Ref Branch</code> as the dimension and <code>COUNT()</code> as the metric can visualize which branches are the most active, helping you understand where development effort is concentrated.
- Performance Metrics per Branch: You can analyze if the review process differs by branch. For example, group the average cycle time by <code>Base Ref Branch</code> to see if pull requests targeting main are processed faster or slower than those targeting a develop branch.

Custom Formulas and Categorization: You can use custom formulas to group various branches into logical categories for simpler, high-level reporting.

- For instance, you could categorize your work into "Production" and "Pre-production" streams using a formula in a dimension like <code>IF(base_ref_branch == 'main', 'Production', 'Pre-production')</code>. This makes it easier to compare the volume and velocity of work destined for different environments.​

- Filtering and Scoping: You can focus your insights on the streams of work that matter most by filtering on the destination branch.
 - Production Deployments: Create reports that only include pull requests merged into your main production branch by using a filter like <code>Base Ref Branch = main</code>.
 - Release Monitoring: Use a regex filter such as <code>Base Ref Branch ~ ^release- </code>to monitor all pull requests related to a specific release cycle.
 - Excluding Hotfixes: If you want to analyze feature work separately, you can exclude urgent fixes with a filter like <code>Base Ref Branch !~ ^hotfix-</code>.
- Reporting and Analysis: Using <code>Base Ref Branch</code> as a dimension allows you to compare different development streams.
 - Activity per Branch: A bar chart with <code>Base Ref Branch</code> as the dimension and <code>COUNT()</code> as the metric can visualize which branches are the most active, helping you understand where development effort is concentrated.
 - Performance Metrics per Branch: You can analyze if the review process differs by branch. For example, group the average cycle time by <code>Base Ref Branch</code> to see if pull requests targeting main are processed faster or slower than those targeting a develop branch.
- Custom Formulas and Categorization: You can use custom formulas to group various branches into logical categories for simpler, high-level reporting.
 - For instance, you could categorize your work into "Production" and "Pre-production" streams using a formula in a dimension like <code>IF(base_ref_branch == 'main', 'Production', 'Pre-production')</code>. This makes it easier to compare the volume and velocity of work destined for different environments.​

Issues and PRs > Base ref | Branch

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_ref_name`
Gitlab (PRs)	`target_branch`
Bitbucket (PRs)	`destination.branch.name`
Azure DevOps (PRs, Issues)	`targetRefName`
JIRA	N/A
ClickUp	N/A
Trello	N/A

Issues and PRs > Base ref | Branch

Reporting Use Cases