Skip to main content

Issues and PRs > Assignees

Tom Williams avatar
Written by Tom Williams
Updated this week

Dataset: Issues & Pull Requests

Entity: Pull Requests, Issues

Field ID: assignee_usernames

Type: Select list

Description: The list of usernames from people assigned to the issue or pull request. Note that usernames are app-specific.

Source: App

Transformation logic: N/A

From:

Github (PRs, Issues)

assignees

Gitlab (PRs, Issues)

assignees

Bitbucket (PRs)

N/A - no concepts of assignment

Azure DevOps (PRs, Issues)

N/A - no concepts of assignment

JIRA (Issues)

assignees

ClickUp (Issues)

assignees

Trello (Issues)

members

Reporting Use Cases

The assignee_usernames field is crucial for understanding workload distribution, tracking individual responsibilities, and managing team capacity. As a list of strings, it can be used in several powerful ways for filtering and reporting.

  • Filtering and Workload Management: You can create personalized or team-specific views by filtering items based on this field.

    • Use the contains operator to find all work assigned to a specific person (e.g., assignee_usernames contains "john.doe").

    • Use the includes me operator to create dynamic reports that show only items assigned to the person viewing the widget.

    • Identify untriaged or unassigned work by filtering for items where the list of assignees is empty, using the length = 0 operator.

  • Reporting and Aggregation: To accurately report on a per-user basis, you need to treat each assignee as a separate entity. This is done using the FLATTEN function in a custom formula.

    • Workload Distribution: To create a bar chart showing the number of open issues per assignee, you can use FLATTEN(assignee_usernames) as the dimension and COUNT() as the metric. This will count each issue once for every person assigned to it, giving you a clear view of individual workloads.

  • Custom Formulas and Advanced Metrics: The list nature of this field allows for more advanced calculations.

    • Collaboration Analysis: You can analyze the number of assignees on each item by using the LENGTH() function. For example, a metric like AVG(LENGTH(assignee_usernames)) can tell you the average number of people assigned to each task, indicating patterns of individual versus collaborative work.

    • Conditional Counting: You can use the CONTAINS() function within a metric to count items assigned to a specific person without filtering the entire widget. For instance, COUNT_IF(CONTAINS(assignee_usernames, "jane.doe")) could be a column in a report showing a team's overall work, highlighting how much of it falls to a specific member.

Did this answer your question?