diff options
Diffstat (limited to 'doc/development/work_items.md')
| -rw-r--r-- | doc/development/work_items.md | 32 |
1 files changed, 31 insertions, 1 deletions
diff --git a/doc/development/work_items.md b/doc/development/work_items.md index 3625f85eb82..f15c66ae847 100644 --- a/doc/development/work_items.md +++ b/doc/development/work_items.md @@ -36,7 +36,7 @@ Here are some problems with current issues usage and why we are looking into wor differences in common interactions that the user needs to hold a complicated mental model of how they each behave. - Issues are not extensible enough to support all of the emerging jobs they need to facilitate. -- Codebase maintainability and feature development becomes a bigger challenge as we grow the Issue type. +- Codebase maintainability and feature development becomes a bigger challenge as we grow the Issue type beyond its core role of issue tracking into supporting the different work item types and handling logic and structure differences. - New functionality is typically implemented with first class objects that import behavior from issues via @@ -204,3 +204,33 @@ provide a smooth migration path of epics to WIT with minimal disruption to user We will move towards work items, work item types, and custom widgets (CW) in an iterative process. For a rough outline of the work ahead of us, see [epic 6033](https://gitlab.com/groups/gitlab-org/-/epics/6033). + +## Redis HLL Counter Schema + +We need a more scalable Redis counter schema for work items that is inclusive of Plan xMAU, Project Management xMAU, Certify xMAU, and +Product Planning xMAU. We cannot aggregate and dedupe events across features within a group or at the stage level with +our current Redis slot schema. + +All three Plan product groups will be using the same base object (`work item`). Each product group still needs to +track MAU. + +### Proposed aggregate counter schema + +```mermaid +graph TD + Event[Specific Interaction Counter] --> AC[Aggregate Counters] + AC --> Plan[Plan xMAU] + AC --> PM[Project Management xMAU] + AC --> PP[Product Planning xMAU] + AC --> Cer[Certify xMAU] + AC --> WI[Work Items Users] +``` + +### Implementation + +The new aggregate schema is already implemented and we are already tracking work item unique actions +in [GitLab.com](https://gitlab.com). + +For implementation details, this [MR](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/93231) can be used +as a reference. The MR covers the definition of new unique actions, event tracking in the code and also +adding the new unique actions to the required aggregate counters. |