Skip to main content

Issues and PRs > Title

Written by Tom Williams
Updated over 2 weeks ago

Dataset: Issues & Pull Requests

Entity: Pull Requests, Issues

Field ID: title

Type: Text

Description: The name or title of the item.

Source: App

Transformation logic: N/A

From:

Github (PRs, Issues)

title

Gitlab (PRs, Issues)

title

Bitbucket (PRs)

title

Azure DevOps (PRs, Issues)

PR: title
​Issue: System.Title

Jira (Issues)

summary

ClickUp (Issues)

name

Trello (Issues)

name

Reporting Use Cases

The title 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 Title ~ "auth".

    • 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 Title !~ "(WIP|Draft)" 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 REGEX_EXTRACT(title, "\\[[A-Z]+\\]").

    • 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 REGEX_EXTRACT(title, "TICKET-\\d+"), allowing you to group all related pull requests.

Did this answer your question?