Dataset: Issues & Pull Requests
Entity: Pull Requests, Issues
Field ID: past_assignee_usernames
Type: Select list
Description: The list of usernames from people previously assigned to the issue or pull request. Note that usernames are app-specific.
Source: App
Transformation logic:
GitHub, GitLab, Jira, and Trello: List of unassigned users, from historical events
ClickUp: Since this app does not expose historical events, Keypup tracks changes on the
assigneesfield to detect the people who were previously assigned. This tracking only applies to unassignments performed after the project has been connected to Keypup.
From: |
|
Github (PRs, Issues) | Collected from unassigned events |
Gitlab (PRs, Issues) | Collected from unassigned events |
Bitbucket (PRs) | N/A - no concepts of assignment |
Azure DevOps (PRs, Issues) | N/A - no concepts of assignment |
JIRA (Issues) | Collected from unassigned events |
ClickUp (Issues) | Generated by observing changes on the |
Trello (Issues) | Collected from unassigned events |
Reporting Use Cases
The Past Assignees field provides a complete historical record of everyone who was previously assigned to an item, making it invaluable for analyzing workflow stability and assignment churn. As a list of strings, it is primarily used for filtering and for creating advanced metrics related to process efficiency.
Filtering for Historical Context: You can create reports based on the entire history of an item's ownership, not just its current state.
Find All Touched Items: To see every item that a specific person has ever been assigned to (even if they are no longer the owner), you can use a filter like
Past Assignees contains "jane.doe".Isolate Reassigned Work: A key use case is to focus on items that have been handed off at least once. A filter where
Past Assignees length > 0will create a report of all items that have experienced assignment churn.
Measuring Assignment Churn: The most powerful application of this field is to quantify the frequency of handoffs, which can be a sign of process inefficiency or shifting priorities.
Number of Handoffs: You can create a custom dimension in a list report with the formula
LENGTH(past_assignee_usernames)and sort by it to immediately identify the items that have been passed around the most.Average Churn Rate: You can build a KPI to track the average number of times an item is reassigned before it's completed using the formula
AVG(LENGTH(past_assignee_usernames)). A high or rising average for this metric suggests there may be issues with initial task triage or that priorities are unstable.