All Collections
Data & operations
Issues & Pull Requests dataset
Issues and PRs > Resolving PR IDs (System)
Issues and PRs > Resolving PR IDs (System)
Tom Azernour avatar
Written by Tom Azernour
Updated over a week ago

Dataset: Issues & Pull Requests

Entity: Issues

Field ID: resolving_pull_request_sysids

Type: List of text values

Description: The list of pull request System IDs (Keypup IDs) that resolve an issue via auto-closing keywords.

It can be used to:

  • count the number of resolving pull requests on each issue

  • see a list of resolved issues from a specific pull request by configuring a drilldown report on the resulting values (select all issues where the resolving pull request ids contain the selected PR id).

Source: Calculated

Transformation logic:

  • Pull Requests: This field will always be an empty array (a pull request cannot resolve another pull request)

  • Issues: The list of system IDs (Keypup-generated IDs) from pull requests that resolve the issue. Resolving pull requests are pull requests that reference the issue via auto-closing keywords.

Definition of resolving pull requests:

A resolving pull request is a pull request that:

  • Contains an auto-closing keyword to an issue

  • Has a base ref that has not been used as a head ref by a previous pull request associated with the issue

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.


Github (PRs)

Gitlab (PRs)








Did this answer your question?