Dataset: Issues & Pull Requests
Entity: Pull Requests, Issues
Field ID: owner_usernames
Type: Select list
Description: The list of usernames from people considered owners of the item. For pull requests, this is the author. For issues, this is the list of assignees. Owners are expected to make the item (issue or pull request) move forward in the project management flow.
This field was created to simplify filtering across issues and pull requests, especially dashboard-wide filtering. Using the owners field you can easily filter an entire dashboard of issue and pull request metrics for a specific team member or squad.
Source: Calculated
Transformation logic:
Issues: This is the list of assignees
Pull requests: this is the author (single-element list)
From: |
|
Github (PRs, Issues) | Calculated |
Gitlab (PRs, Issues) | Calculated |
Bitbucket (PRs) | Calculated |
Azure DevOps (PRs, Issues) | Calculated |
JIRA (Issues) | Calculated |
ClickUp (Issues) | Calculated |
Trello (Issues) | Calculated |
Reporting Use Cases
The Owners field is a powerful computed field that consolidates responsibility, showing who is expected to move an item forward (the author for a pull request, or the assignees for an issue). This makes it essential for tracking workload, managing personal tasks, and ensuring all work is accounted for.
Filtering for Workload Management: This field is ideal for creating personalized or team-based views of responsibility.
Personal Dashboards: The most common use is to create a "My Work" widget by using a filter where
Owners includes me. This dynamically shows each user the items they are responsible for.Team Workload: You can see all items owned by a specific team by using a filter like
Owners contains any of "user1,user2".Find Unowned Work: A critical use case is to identify issues that have no clear owner and might be stalled. You can do this by creating a report where
Owners length = 0.
Reporting on Workload Distribution: To accurately report on the workload of each individual, you must use the
FLATTENfunction to treat each owner in the list separately.Items per Owner: To create a bar chart showing the number of open items each person is responsible for, use a custom formula dimension like
FLATTEN(owner_usernames)with aCOUNT()metric. This provides a clear, at-a-glance view of how work is distributed across the team.
Custom Formulas for Collaboration Analysis: You can analyze patterns of ownership to understand how your team collaborates.
Co-ownership Rate: A metric like
AVG(LENGTH(owner_usernames))can tell you the average number of owners per item. A value close to 1 suggests work is typically owned by individuals, while a higher value indicates a more collaborative, co-owned approach.Count of Unique Owners: You can measure the breadth of work distribution with the formula
COUNT_DISTINCT(FLATTEN(owner_usernames)), which calculates the total number of unique people owning work in a given period.