Skip to main content

Common Field: Project

Arnaud Lachaume avatar
Written by Arnaud Lachaume
Updated this week

Dataset: All

Entity: -

Field ID: project_name

Type: Text

Description: The name of the project associated with the record

Source: App

Transformation logic: N/A

From:

Github (PRs, Issues)

Source project

Gitlab (PRs, Issues)

Source project

Bitbucket (PRs)

Source project

Azure DevOps (PRs, Issues)

Source project

JIRA (Issues)

Source project

ClickUp (Issues)

Source project

Trello (Issues)

Source project

Reporting Use Cases

The Project field is one of the most fundamental attributes for reporting, as it allows you to scope your analysis to a specific codebase or workstream. Depending on the dataset, a "project" can be a source code repository (like a GitHub repository) or a project management project (like a Jira project).

  • Filtering and Scoping: Its most common use is to filter your widgets to focus on the work within a single or a group of projects.

    • To create a dashboard for a single repository, you can apply a filter like Project = "my-awesome-app".

    • To analyze activity across all your backend microservices, you could use a regex filter such as Project ~ "-service$".

    • You can also exclude non-production or legacy projects from your reports with a filter like Project != "legacy-archive".

  • Reporting on Work Distribution: When used as a dimension, project_name is the primary way to compare activity and performance across different parts of your organization.

    • A bar chart with Project as the dimension and COUNT() as the metric will instantly show you which repositories or projects have the most activity (e.g., the most issues or pull requests).

    • You can benchmark performance by creating a list report with Project as the dimension and a metric like AVG(merged_at - created_at) to see the average pull request cycle time for each repository.

  • Custom Formulas for High-Level Grouping: For organizations with many projects or repositories, you can use custom formulas to group them into higher-level categories for simplified reporting.

    • A custom dimension with a formula like IF(project_name ~ "mobile", "Mobile Portfolio", "Web Portfolio") allows you to roll up your metrics and analyze performance at a portfolio or team level, rather than on a per-repository basis.

Did this answer your question?