Dataset: Issues & Pull Requests
Entity: Pull Requests, Issues
Field ID: last_assigned_at
Type: Datetime
Description: The datetime at which a user was last assigned to the item.
Source: Calculated
Transformation logic:
GitHub, GitLab, Jira, and Trello: It is the datetime of the last
user assignedevent, which happens when a user is added to the list of assignees.ClickUp: Since this app do not expose historical events, Keypup tracks changes on the
assigneesfield to detect this timestamp. This tracking only applies to assignments performed after the project has been connected to Keypup. This field remains null when we detect that reviewers were assigned prior to importing the issue or pull request to Keypup because we cannot know precisely when this assignment occurred.
From: |
|
Github (PRs, Issues) | Calculated |
Gitlab (PRs, Issues) | Calculated |
Bitbucket (PRs) | N/A - no concepts of assignment |
Azure DevOps (PRs, Issues) | N/A - no concepts of assignment |
JIRA (Issues) | Calculated |
ClickUp (Issues) | Inferred from updates |
Trello (Issues) | Calculated |
Reporting Use Cases
The Last Assigned At field provides a timestamp for the most recent assignment change on an item, making it ideal for tracking ownership transfers and identifying work that has been recently reprioritized or handed off.
Filtering for Recent Handoffs: You can create reports that focus on items that have recently changed hands, which is useful for managers tracking team dynamics.
To see all work that was reassigned in the last week, you can use a filter like
Last Assigned At in the previous 7 days.To find items that haven't been reassigned in a long time (potentially indicating stable ownership or stale work), you could filter where
Last Assigned At before "6 months ago".
Calculating Time with Current Assignee: For open items, you can measure how long the current assignee has been responsible for the task.
A custom dimension with the formula
ROUND((NOW() - last_assigned_at) / DAY())will show the number of days since the last handoff, helping to identify items that might be stalled with their current owner.
Analyzing Assignment Churn: By comparing the first and last assignment dates, you can identify items that have been passed between team members multiple times.
You can calculate the total time an item has been in an "assigned" state with the formula
(last_assigned_at - assigned_at) / DAY(). A high value could indicate that the item has changed hands frequently or that there was a long gap between its first and last assignment.
Tracking Re-triage Trends: By using this field as a dimension, you can visualize the frequency of reassignments over time.
A line chart with
YEAR_MONTH(last_assigned_at)as the dimension andCOUNT()as the metric can show you if there are periods with an unusually high number of reassignments, which might correlate with changes in project priorities or team structure.