Keypup

Dataset: Issues &amp; Pull Requests

Field ID: <code>resolved_issue_last_assigned_at</code>

Description: The latest first assignment date among all resolved issues. This field only considers the <code>assigned_at</code> field of issues, not the <code>last_assigned_at</code> field.

Pull Requests: The latest occurrence of all <code>assigned_at</code> fields from resolved issues. The <code>null</code> values are ignored. A <code>null</code> value is returned only if all <code>assigned_at</code> values are <code>null</code>. Resolved issues are issues that are referenced by a <a href="https://docs.keypup.io/en/articles/12324330-definition-resolving-pull-request">resolving pull request</a>.

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

- Pull Requests: The latest occurrence of all <code>assigned_at</code> fields from resolved issues. The <code>null</code> values are ignored. A <code>null</code> value is returned only if all <code>assigned_at</code> values are <code>null</code>. Resolved issues are issues that are referenced by a <a href="https://docs.keypup.io/en/articles/12324330-definition-resolving-pull-request">resolving pull request</a>. 
- Issues: Not applicable. This field will always be <code>null</code>.

The <code>Resolved Issue Last Assigned At</code> field is a specialized timestamp that captures the most recent assignment date among all issues resolved by a pull request. It effectively marks the final handoff or the last moment of ownership decision before the implementation was completed, making it useful for analyzing the final stages of your planning and delivery cycle.

Calculating "Final Handoff to Merge" Time: The primary use of this field is to measure the duration from the last assignment decision on an issue to the final merge of the code that resolves it.

- You can calculate this with the custom formula <code>(merged_at - resolved_issue_last_assigned_at) / DAY()</code>. A high value for this metric could indicate a delay between when an issue was finally assigned and when the corresponding code was delivered, or it might highlight last-minute changes in ownership right before the finish line.

Analyzing the Duration of Assignment Churn: By comparing this timestamp with the resolved_issue_first_assigned_at field, you can measure the total time span over which an issue (or group of issues) was passed between team members.

- The formula <code>(resolved_issue_last_assigned_at - resolved_issue_first_assigned_at) / DAY()</code> calculates the total duration of the "assignment phase." A long period here suggests that a feature or bug was reassigned multiple times or sat with different owners for a long time before being resolved.

Filtering for Recent Re-assignments: You can create reports that focus on pull requests that are the result of recent changes in planning or prioritization.

- To see all recently merged pull requests that resolved an issue that was handed off in the last week, you could use a filter like <code>Resolved Issue Last Assigned At in the previous 7 days</code>.

- Calculating "Final Handoff to Merge" Time: The primary use of this field is to measure the duration from the last assignment decision on an issue to the final merge of the code that resolves it.
 - You can calculate this with the custom formula <code>(merged_at - resolved_issue_last_assigned_at) / DAY()</code>. A high value for this metric could indicate a delay between when an issue was finally assigned and when the corresponding code was delivered, or it might highlight last-minute changes in ownership right before the finish line.
- Analyzing the Duration of Assignment Churn: By comparing this timestamp with the resolved_issue_first_assigned_at field, you can measure the total time span over which an issue (or group of issues) was passed between team members.
 - The formula <code>(resolved_issue_last_assigned_at - resolved_issue_first_assigned_at) / DAY()</code> calculates the total duration of the "assignment phase." A long period here suggests that a feature or bug was reassigned multiple times or sat with different owners for a long time before being resolved.
- Filtering for Recent Re-assignments: You can create reports that focus on pull requests that are the result of recent changes in planning or prioritization.
 - To see all recently merged pull requests that resolved an issue that was handed off in the last week, you could use a filter like <code>Resolved Issue Last Assigned At in the previous 7 days</code>.

Issues and PRs > Resolved Issue last assigned 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)	Calculated
Azure DevOps (PRs, Issues)	Calculated
JIRA (Issues)	N/A
ClickUp (Issues)	N/A
Trello (Issues)	N/A

Issues and PRs > Resolved Issue last assigned at

Reporting Use Cases