Skip to main content

Common Field: Source App

Arnaud Lachaume avatar
Written by Arnaud Lachaume
Updated this week

Dataset: All

Entity: -

Field ID: source_app

Type: Text

Description: The name of the application associated with the record.

Source: App

Transformation logic: N/A

From:

Github (PRs, Issues)

Repositories: github
​Projects: github-projects

Gitlab (PRs, Issues)

gitlab (cloud) or gitlab-hosted (hosted instance)

Bitbucket (PRs)

bitbucket (cloud) or bitbucket-hosted (data center)

Azure DevOps (PRs, Issues)

azure-devops (cloud) or azure-devops-hosted (server instance)

Jira (Issues)

jira (cloud) or jira-hosted (data center)

ClickUp (Issues)

clickup

Trello (Issues)

trello

Reporting Use Cases

The Source App field is a critical attribute for any organization that uses multiple integrated tools, as it identifies the platform where the data originated (e.g., "github", "jira", "gitlab"). Its primary purpose is to allow for platform-specific analysis and to enable the creation of consistent, unified metrics across different systems.

  • Filtering for Platform-Specific Analysis: This is the most common use of the field. It allows you to create reports that focus on a single tool.

    • To build a dashboard that only shows your project management data, you could apply a filter where Source App equals any of "jira,trello".

    • To analyze your code-related activities, you would filter where Source App equals any of "github,gitlab,bitbucket".

  • Reporting on Cross-Platform Activity: When used as a dimension, this field allows you to compare the volume and type of activity across your different tools.

    • A bar chart with Source App as the dimension and COUNT() as the metric can show you how many items are being created in Jira versus GitHub, for example.

  • Creating Unified Cross-Platform Metrics: This is the most powerful use case. Since different platforms have different features (e.g., GitHub's formal review system vs. GitLab's approvals), you can use Source App in custom formulas to handle these differences and create a single, consistent metric.

    • For example, to calculate a reliable "Time to Start Review" metric across all platforms, you could use a custom formula like IF(source_app == "github", first_review_created_at - review_requested_at, first_comment_after_review_requested_at - review_requested_at). This formula uses the precise GitHub timestamp when available and falls back to a reliable approximation for other platforms, giving you a single, unified KPI.

Did this answer your question?