Dataset: Issues & Pull Requests
Entity: Pull Requests
Field ID: resolved_issue_project_names
Type: List of text values
Description: The list of projects 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
projectfield inherited from issues resolved by the pull request. Identical projects 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 Project Names field is a powerful attribute for understanding the true business context of your development work. It provides a complete list of all the projects that the issues resolved by a pull request belong to, which is essential for tracking cross-repository dependencies and analyzing team efforts at a portfolio level.
Filtering by Impacted Project: You can create reports that show all the coding work (pull requests) that has impacted a specific project, even if that work was done in a different repository.
To find all pull requests that resolved issues in "Project-Alpha", you would use a filter like
Resolved Issue Project Names contains "Project-Alpha".You can also identify pull requests that have a wide-ranging impact by filtering for those that resolve issues in more than one project:
Resolved Issue Project Names length > 1. This is great for spotting work on shared libraries or core services.
Analyzing Work Distribution by Project: The most important use of this field is to see which projects are driving the most development work, regardless of where the code is being written. To do this accurately, you must use the
FLATTENfunction.You can create a bar chart showing the number of pull requests generated by each project's issues. Use a custom formula dimension like
FLATTEN(resolved_issue_project_names)with aCOUNT()metric to visualize your development efforts from a project-centric perspective.
Measuring Cross-Project Impact: You can quantify how often your pull requests impact multiple projects, which is a key indicator of work on shared components.
A custom formula metric like
AVG(LENGTH(resolved_issue_project_names))will calculate the average number of projects impacted by a single pull request. A high number suggests that your team is frequently working on foundational, cross-cutting concerns.