Dataset: Issues & Pull Requests

Entity: Issues

Field ID: resolving_pr_label_names

Type: List of text values

Description: The combination of labels from all resolving PRs (via auto-closing keywords), deduplicated and sorted. It is only applicable to issues.

It can be used to get a quick overview of the type of work addressed by the resolving pull requests (e.g. the field contains "bugfix" and "hotfix" labels, indicating that this issue was addressed in a bug-fixing body of work).

Source: Calculated

Transformation logic:

Definition of resolving pull requests:

A resolving pull request is a pull request that:

This last condition ensures that release PRs (e.g. PR from master to staging then staging to production) do not get considered as resolving if they follow a proper implementation PR (e.g. from my-feature-branch to master), even though they contain references to issues through commits.

This condition replaces the rule from GitHub, GitLab, and Bitbucket that resolving pull requests must target the main branch. This condition is not practical for Keypup since the main branch can change over time. Using this definition would mean that any resolving PR preceding a change of main branch would no longer be considered as resolving, which would impact historical reporting.

The Keypup definition also brings some flexibility in case of emergency releases. If you push an emergency fix referencing an issue to the main branch and then release this fix through release PRs, then the first release PR will be considered as a resolving PR (GitHub/GitLab/Bitbucket would simply ignore it). This information can then be used for incident reporting in Keypup.