Create database records to track onboarding progress
Problem
As a product manager, we need some way to track the progress of a namespace as it moves through the onboarding process. Moreover, we need to utilize that data to prioritize communication with the user and get them to take the next step in their onboarding.
Data
All data should be recorded at the namespace level
-
(1) Converted to paid (gitlab-org/gitlab!48497 (merged)) -
(2) First Git Write operation (gitlab-org/gitlab!48924 (merged)) -
(3) First MR (gitlab-org/gitlab!49002 (merged)) -
(4) First git pull (gitlab-org/gitlab!49007 (merged)) -
(5) First clone (Alex)(This is identical to git pull) -
(5) First pipeline created (successful or not) (gitlab-org/gitlab!49010 (merged)) -
(6) First user added (gitlab-org/gitlab!49383 (merged)) -
(7) Trial started (Nicolas) (gitlab-org/gitlab!49351 (merged)) -
(8) Enabled required merge approvals (Nicolas) (gitlab-org/gitlab!51987 (merged)) -
(9) Enabled code owners (Nicolas) (gitlab-org/gitlab!51925 (merged)) -
(10) Created scoped labels (Nicolas) (gitlab-org/gitlab!51386 (merged)) -
(11) Enabled/ran a security scan (Nicolas) gitlab-org/gitlab!52328 (merged) -
(12) MR that auto-closes an open issue (Nicolas) (gitlab-org/gitlab!51903 (merged)) -
(13) Issue created based on design requirements product#1652 (comment 491945495) (gitlab-org/gitlab!53611 (merged)) -
(14) First repository imported -
(15) First repository mirrored
Reasoning
By recording these actions in a database, we can use them to trigger communication logic within the product (.com or self-managed).
Edited by Nicolas Dular