Keypup

Dataset: Issues &amp; Pull Requests

Field ID: <code>resolved_issue_last_closed_at</code>

Description: The latest closure date among all resolved issues (via <a href="https://docs.keypup.io/en/articles/196-how-to-link-pull-requests-to-issues">auto-closing keywords</a>).

Pull Requests: The latest occurrence of all <code>closed_at</code> fields inherited from issues that are resolved by the pull request. The <code>null</code> values are ignored. A <code>null</code> value is returned only if all <code>closed_at</code> values are <code>null</code>. Resolved issues are issues that are referenced by a pull request via <a href="https://docs.keypup.io/en/articles/196-how-to-link-pull-requests-to-issues">auto-closing keywords</a>.

Issues: Not applicable. This field will always be <code>null</code>.

- Pull Requests: The latest occurrence of all <code>closed_at</code> fields inherited from issues that are resolved by the pull request. The <code>null</code> values are ignored. A <code>null</code> value is returned only if all <code>closed_at</code> values are <code>null</code>. Resolved issues are issues that are referenced by a pull request via <a href="https://docs.keypup.io/en/articles/196-how-to-link-pull-requests-to-issues">auto-closing keywords</a>. 
- Issues: Not applicable. This field will always be <code>null</code>.

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

A resolving pull request is a pull request that:

Contains an <a href="https://docs.keypup.io/en/articles/196-how-to-link-pull-requests-to-issues">auto-closing keyword</a> to an issue

Has a <code>state</code> equal to <code>OPEN</code> or <code>MERGED</code>, not <code>CLOSED</code>

Has a <code>base ref</code> that has not been used as a <code>head ref</code> by a previous pull request associated with the issue

- Contains an <a href="https://docs.keypup.io/en/articles/196-how-to-link-pull-requests-to-issues">auto-closing keyword</a> to an issue
- Has a <code>state</code> equal to <code>OPEN</code> or <code>MERGED</code>, not <code>CLOSED</code>
- Has a <code>base ref</code> that has not been used as a <code>head ref</code> by a previous pull request associated with the issue

This last condition ensures that release PRs (e.g. PR from <code>master</code> to <code>staging</code> then <code>staging</code> to <code>production</code>) do not get considered as resolving if they follow a proper implementation PR (e.g. from <code>my-feature-branch</code> to <code>master</code>), 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 the 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.

Issues and PRs > Resolved Issue last closed at

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	Inferred from GitHub auto-closing keywords
Gitlab	Inferred from GitLab auto-closing keywords
Bitbucket	Inferred from Bitbucket auto-closing keywords
JIRA	N/A
ClickUp	N/A
Trello	N/A