Dataset: Issues & Pull Requests
Entity: Pull Requests
Field ID: resolved_issue_author_usernames
Type: List of text values
Description: The combination of authors from all resolved issues (via auto-closing keywords), deduplicated, and sorted. It is only applicable to pull requests.
Source: Calculated
Transformation logic:
Pull Requests: Aggregate all results of the
authorfield from resolved issues. Identical authors are deduplicated. Resolved issues are issues that are referenced by a resolving pull request.Issues: Not applicable. This field will always be an empty array
[].
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 |
Reporting Use Cases
The Resolved Issue Authors field provides a direct link between a pull request and the person who originally created the issue(s) it resolves. This is invaluable for analyzing communication patterns, understanding the origin of work, and measuring the impact of different stakeholders.
Analyzing Workflow Patterns: This field allows you to see the relationship between who reports the work and who implements it.
You can categorize pull requests to distinguish between developers fixing their own issues versus those picking up work from others. A custom formula dimension like
IF(CONTAINS(resolved_issue_author_usernames, author_username), "Self-Resolved", "Team Collaboration")can highlight patterns of self-service versus cross-functional teamwork.
Reporting on the Origin of Implemented Work: You can use this field to measure the impact of different roles within your organization, such as product managers or QA engineers.
By using the
FLATTENfunction in a dimension(FLATTEN(resolved_issue_author_usernames))with aCOUNT()metric, you can create a bar chart showing which individuals are the source of the most implemented work, effectively measuring their influence on the development pipeline.
Filtering by Issue Creator: You can scope your reports to show all the development work that originated from a specific person or group.
To see all pull requests that resolve issues created by your product team, you could use a filter like
Resolved Issue Authors contains any of "product.manager1,product.manager2". This helps you track the implementation progress of planned features.