Keypup

Dataset: Issues &amp; Pull Requests

Field ID: <code>resolving_pr_first_closed_at</code>

Description: The earliest closure date among all resolving PRs. (via <a href="https://docs.keypup.io/en/articles/196-how-to-link-pull-requests-to-issues">auto-closing keywords)</a>. It is only applicable to issues.

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

Issues: The earliest occurrence of all <code>closed_at</code> fields from <a href="https://docs.keypup.io/en/articles/12324330-definition-resolving-pull-request">resolving pull requests</a>. 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>.

- Pull Requests: Not applicable. This field will always be <code>null</code>.
- Issues: The earliest occurrence of all <code>closed_at</code> fields from <a href="https://docs.keypup.io/en/articles/12324330-definition-resolving-pull-request">resolving pull requests</a>. 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>.

The <code>Resolving PR First Closed At</code> field captures the timestamp when the first pull request linked to an issue was closed (either merged or discarded). This is a key milestone for measuring the initial development cycle and identifying issues that require multiple attempts or long verification periods.

Measuring "Time to Initial Implementation": This field allows you to calculate how long it took from an issue's creation to the first completed development attempt.

- You can measure this initial cycle time with the custom formula <code>(resolving_pr_first_closed_at - created_at) / DAY()</code>.

Identifying Rework and Verification Bottlenecks: By comparing this timestamp to the issue's final closure date, you can see how much time was spent after the first PR was finished.

- The formula <code>(closed_at - resolving_pr_first_closed_at) / DAY()</code> calculates this "post-implementation" phase. A large gap here often indicates either a long QA process or that the first PR didn't fully solve the problem, requiring subsequent PRs (rework).

Filtering for Recent Activity: You can use this field to find issues where development has recently finished, even if the issue itself is still open for testing.

- Use a filter like <code>Resolving PR First Closed At in the previous 7 days</code> to identify issues that have just moved out of the active coding phase.

- Measuring "Time to Initial Implementation": This field allows you to calculate how long it took from an issue's creation to the first completed development attempt.
 - You can measure this initial cycle time with the custom formula <code>(resolving_pr_first_closed_at - created_at) / DAY()</code>.
- Identifying Rework and Verification Bottlenecks: By comparing this timestamp to the issue's final closure date, you can see how much time was spent after the first PR was finished.
 - The formula <code>(closed_at - resolving_pr_first_closed_at) / DAY()</code> calculates this "post-implementation" phase. A large gap here often indicates either a long QA process or that the first PR didn't fully solve the problem, requiring subsequent PRs (rework).
- Filtering for Recent Activity: You can use this field to find issues where development has recently finished, even if the issue itself is still open for testing.
 - Use a filter like <code>Resolving PR First Closed At in the previous 7 days</code> to identify issues that have just moved out of the active coding phase.

Issues and PRs > Resolving PR first 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 (PRs, Issues)	Calculated
Gitlab (PRs, Issues)	Calculated
Bitbucket (PRs)	N/A
Azure DevOps (PRs, Issues)	Calculated
JIRA (Issues)	Calculated
ClickUp (Issues)	Calculated
Trello (Issues)	Calculated

Issues and PRs > Resolving PR first closed at

Reporting Use Cases