Dataset: Issues & Pull Requests
Entity: Pull Requests, Issues
Field ID: project_source
Type: Text
Description: The name of the original project the issue or pull request comes from. This field is always equal to the Project field, except for GitHub Projects, where it is equal to the original repository the item comes from.
Source: App
Transformation logic:
For GitHub Project: the field is equal to the source repository the issue or pull request comes from.
All other types of projects: the field is equal to the Project field.
From: |
|
Github (PRs, Issues) | Repository: the field is equal to the project field GitHub Project: the field is equal to the source repository the issue or pull request comes from. |
Gitlab (PRs, Issues) | Always equal to the project field |
Bitbucket (PRs) | Always equal to the project field |
Azure DevOps (PRs, Issues) | Always equal to the project field |
JIRA (Issues) | Always equal to the project field |
ClickUp (Issues) | Always equal to the project field |
Trello (Issues) | Always equal to the project field |
Reporting Use Cases
The Project Source field is an essential attribute for organizations using GitHub Projects, as it provides a direct link back to the original repository where an issue or pull request lives. Its primary purpose is to enable accurate, repository-level analysis when your reporting is scoped to a cross-repository GitHub Project.
Repository-Level Grouping in GitHub Projects: When you create a widget filtered by a specific GitHub Project (e.g.,
Project = "My Cross-Repo Project"), the work items might come from many different repositories.Project Sourceis the only way to accurately group and analyze that work by its original source.Work Distribution by Repository: To see which repositories contribute the most work to a GitHub Project, you can create a bar chart with
Project Sourceas the dimension andCOUNT()as the metric. This is crucial for understanding the project's composition and activity hotspots.
Calculating Repository-Specific Metrics: This field allows you to calculate performance metrics for individual repositories, even when they are part of a larger, consolidated project view.
Cycle Time per Repository: In a widget focused on a GitHub Project, you can compare the average cycle time of different contributing repositories. Use a list widget with
Project Sourceas the dimension andAVG(merged_at - created_at)as the metric to identify which repositories have faster or slower delivery pipelines within the context of the same project.
Filtering by Original Repository: You can use
Project Sourceto create more granular views within a GitHub Project.For example, if a large GitHub Project board contains items from both a frontend and a backend repository, you can create separate widgets for each by applying a filter like
Project Source = "my-backend-repo", even while keeping the overall dashboard context set to the GitHub Project.