Dataset: Issues & Pull Requests
Entity: Issues
Field ID: resolving_pr_author_usernames
Type: List of text values
Description: The combination of authors from all resolving PRs (via auto-closing keywords), deduplicated and sorted. It is only applicable to issues.
Source: Calculated
Transformation logic:
Pull Requests: Not applicable. This field will always be an empty array
[].Issues: Aggregate all results of the
assigneesfield from resolving pull requests. Identical authors are deduplicated.
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 |
Reporting Use Cases
The Resolving PR Authors field provides a direct link from an issue to the developers who wrote the code to resolve it. This is essential for understanding who is performing the implementation work, regardless of who was originally assigned the issue.
Analyzing Implementation Workload: This field's primary purpose is to accurately attribute implementation work to the correct individuals. To do this, you must use the
FLATTENfunction to analyze each author separately.Issues Implemented per Developer: You can create a bar chart showing the number of issues each developer has implemented. Use a custom formula dimension like
FLATTEN(resolving_pr_author_usernames)with aCOUNT()metric to see who is contributing the most code to resolve issues.
Filtering by Contributor: You can create reports that show all the issues a specific developer has helped implement.
To see every issue that "john.doe" has written code for, you can use a filter like
Resolving PR Author contains "john.doe". This is a powerful way to review an individual's contributions at the issue level, which is especially useful for performance reviews or mentoring.
Comparing Ownership vs. Implementation: You can analyze your workflow to see if the person assigned to an issue is the one who ultimately writes the code.
By creating reports that compare the
assignee_usernameswith theresolving_pr_author_usernames, you can identify how often work is handed off for implementation. A high rate of handoffs could be a normal part of your process or could indicate a need for better initial triage and assignment.