Skip to content

update dbt model table on ea cheat sheet page

Lily Fisher requested to merge master-patch-d654 into master

Why is this change being made?

The EA team has created several new DBT models in workspace_engineering schema:

Table SQL Description
workspace_engineering.internal_issues_enhanced https://gitlab.com/gitlab-data/analytics/-/blob/master/transform/snowflake-dbt/models/workspaces/workspace_engineering/internal_issues_enhanced.sql Similar to engineering_issues, except it does not filter for only part of product issues
workspace_engineering.internal_issues https://gitlab.com/gitlab-data/analytics/-/blob/master/transform/snowflake-dbt/models/workspaces/workspace_engineering/internal_issues.sql Base for workspace_engineering.engineering_issues. We use this table to build other issue DBT models.
workspace_engineering.internal_merge_requests https://gitlab.com/gitlab-data/analytics/-/blob/master/transform/snowflake-dbt/models/workspaces/workspace_engineering/internal_merge_requests.sql Base for workspace_engineering.engineering_merge_requests. We use this table to build other issue DBT models.
workspace_gneering.internal_notes https://gitlab.com/gitlab-data/analytics/-/blob/master/transform/snowflake-dbt/models/workspaces/workspace_engineering/internal_notes.sql Used to query history on MR/issue/epic
workspace_engineering.issues_history https://gitlab.com/gitlab-data/analytics/-/blob/master/transform/snowflake-dbt/models/workspaces/workspace_engineering/issues_history.sql Daily snapshot of issue. We use this for past due metrics.
workspace_engineering.merge_request_rate https://gitlab.com/gitlab-data/analytics/-/blob/master/transform/snowflake-dbt/models/workspaces/workspace_engineering/merge_request_rate.sql This DBT model filters for MR rate by group and department

Add to to the handbook page https://about.gitlab.com/handbook/engineering/metrics/cheat-sheet/#commonly-used-data-models

Closes gitlab-org/quality/engineering-analytics/team-tasks#226

Author Checklist

  • Provided a concise title for this Merge Request (MR)
  • Added a description to this MR explaining the reasons for the proposed change, per say why, not just what
    • Copy/paste the Slack conversation to document it for later, or upload screenshots. Verify that no confidential data is added, and the content is SAFE
  • Assign reviewers for this MR to the correct Directly Responsible Individual/s (DRI)
    • If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the Maintained by section on the page being edited
    • If your manager does not have merge rights, please ask someone to merge it AFTER it has been approved by your manager in #mr-buddies
    • The when to get approval handbook section explains the workflow in more detail
  • If the changes affect team members, or warrant an announcement in another way, please consider posting an update in #whats-happening-at-gitlab linking to this MR
    • If this is a change that directly impacts the majority of global team members, it should be a candidate for #company-fyi. Please work with internal communications and check the handbook for examples.
Edited by Lily Fisher

Merge request reports