Parent Epic: [GitLab.com <> Customers, License, Zuora Integration](https://gitlab.com/groups/gitlab-org/-/epics/3602) ## Overview After we've finished documenting the current state of user flows from both the [UX](https://gitlab.com/groups/gitlab-org/-/epics/3603) and [ENG](https://gitlab.com/groups/gitlab-org/-/epics/3605) perspectives, we should begin creating a roadmap of fixes to solve the [identified problems](https://gitlab.com/groups/gitlab-org/-/epics/3602#problem). To create a roadmap of fixes, we should have all the engineers who worked on the [ENG documentation](https://gitlab.com/groups/gitlab-org/-/epics/3605) get together to discuss the problems they identified and propose a roadmap of fixes. ## Related Issues / MRs: - Add expiration logic for trials to include all dotcom subscriptions and to be background-able and retry-able. https://gitlab.com/gitlab-org/customers-gitlab-com/-/merge_requests/1447 - Expire cleanup phase 1 https://gitlab.com/gitlab-org/customers-gitlab-com/-/merge_requests/1554 ## Next Steps * [ ] Create roadmap of fixes * [ ] Implement fixes ## [WIP] Roadmap of Fixes - We should avoid overwriting fields in Orders table and instead use a Transaction Histories table https://gitlab.com/gitlab-data/analytics/-/issues/5254#note_378737106 - We should have a 1:1:1 relationship where 1 Top-Level Namespace (GitLab.com app) == 1 Customer (Customer's app ) == 1 Customer (Zuora app) https://gitlab.com/gitlab-data/analytics/-/issues/5254#note_378737106 - We should have a 1:1:1 relationship of subscription plans across GitLab.com, Customers, Zuora https://gitlab.com/gitlab-data/analytics/-/issues/5254#note_378737106