Dataset: Issues & Pull Requests

Entity: Pull Requests

Field ID: resolved_issue_label_names

Type: List of text values

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

It can be used to get a quick overview of the type of work addressed by resolved issues (e.g. the field contains "critical-bug" and "medium-bug" labels, indicating that this issue was bundled with other bug fixes).

Source: Calculated

Transformation logic:

Definition of resolved issues:

A resolved issue is an issue that is referenced by a resolving pull request.

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.