Skip to main content

Issues and PRs > Resolving PR Assignees

Arnaud Lachaume avatar
Written by Arnaud Lachaume
Updated over a week ago

Dataset: Issues & Pull Requests

Entity: Issues

Field ID: resolving_pr_assignee_usernames

Type: List of text values

Description: The combination of assignees 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 assignees field from resolving pull requests. Identical assignees 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 Assignees field provides a complete list of all individuals assigned to the pull requests that resolve a specific issue. This is crucial for understanding who is involved in the implementation phase of your work and for analyzing how responsibilities are distributed on the development side.

  • Analyzing Team and Individual Workload: This is the primary use case for this field. It allows you to see which developers are responsible for the implementation of your issues. To do this accurately, you must use the FLATTEN function.

    • Issues Implemented per Person: To see how many issues each developer has implemented, you can create a bar chart with the custom formula dimension FLATTEN(resolving_pr_assignee_usernames) and a COUNT() metric. This provides a clear view of who is taking on the most implementation work.

  • Comparing Planned vs. Actual Ownership: You can compare the issue assignees with the pull request assignees to see if the person who was initially assigned the issue is the same person who is doing the coding.

    • A custom formula dimension like IF(CONTAINS(assignee_usernames, AT_INDEX(resolving_pr_assignee_usernames, 0)), "Same Owner", "Handoff") can flag issues where the work was handed off for implementation, which can be a key insight into your team's workflow.

  • Filtering Issues by Implementer: You can create reports that show all the issues that have been worked on by a specific developer.

    • To see all issues that "jane.doe" has been involved in implementing, you can use a filter like Resolving PR Assignees contains "jane.doe". This is a powerful way to review an individual's contribution at the issue level.

Did this answer your question?