Keypup

Dataset: Issues &amp; Pull Requests

Description: The name or title of the item.

The <code>title</code> field is the primary human-readable identifier for an issue or pull request. While not typically used for aggregation, it is an indispensable element for providing context in list-based reports and can be a surprisingly powerful tool for filtering and categorization when your team follows consistent naming conventions.

Context in Reports: Its most fundamental use is as a dimension in any list widget. Including the title in a report of issues or pull requests is essential for users to understand what each item is about at a glance.

Filtering by Keyword: You can create highly specific reports by searching for keywords within the title, which is especially useful for finding related work that may not share the same labels.

- Find Related Work: To find all pull requests related to your authentication system, you could use a filter like <code>Title ~ "auth"</code>.
- Enforce Naming Conventions: You can audit your team's processes by finding pull requests that don't adhere to your standards. For example, a filter like <code>Title !~ "(WIP|Draft)"</code> on open PRs can help you find work that has not been properly marked as a work-in-progress.

Custom Formulas for Data Extraction: If your titles follow a predictable pattern, you can use custom formulas to extract structured data for better reporting.

- Categorize by Prefix: If your team uses prefixes like "[BUG]" or "[FEATURE]", you can create a custom dimension to categorize your work with a formula like <code>REGEX_EXTRACT(title, "\\[[A-Z]+\\]")</code>.
- Link to External Systems: If titles include references to external tickets (e.g., "Fixes TICKET-123"), you can extract that ID with a formula like <code>REGEX_EXTRACT(title, "TICKET-\\d+")</code>, allowing you to group all related pull requests.

- Context in Reports: Its most fundamental use is as a dimension in any list widget. Including the title in a report of issues or pull requests is essential for users to understand what each item is about at a glance.
- Filtering by Keyword: You can create highly specific reports by searching for keywords within the title, which is especially useful for finding related work that may not share the same labels.
 - Find Related Work: To find all pull requests related to your authentication system, you could use a filter like <code>Title ~ "auth"</code>.
 - Enforce Naming Conventions: You can audit your team's processes by finding pull requests that don't adhere to your standards. For example, a filter like <code>Title !~ "(WIP|Draft)"</code> on open PRs can help you find work that has not been properly marked as a work-in-progress.
- Custom Formulas for Data Extraction: If your titles follow a predictable pattern, you can use custom formulas to extract structured data for better reporting.
 - Categorize by Prefix: If your team uses prefixes like "[BUG]" or "[FEATURE]", you can create a custom dimension to categorize your work with a formula like <code>REGEX_EXTRACT(title, "\\[[A-Z]+\\]")</code>.
 - Link to External Systems: If titles include references to external tickets (e.g., "Fixes TICKET-123"), you can extract that ID with a formula like <code>REGEX_EXTRACT(title, "TICKET-\\d+")</code>, allowing you to group all related pull requests.

Issues and PRs > Title

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, Issues)	`title`
Gitlab (PRs, Issues)	`title`
Bitbucket (PRs)	`title`
Azure DevOps (PRs, Issues)	`title`
JIRA (Issues)	`summary`
ClickUp (Issues)	`name`
Trello (Issues)	`name`

Issues and PRs > Title

Reporting Use Cases