See parent task for more context.
Note that the parent task documents more slicing options than just project / language. Those additional options can be added at the same time if it does not require much additional work. Otherwise, language and project are sufficient for the time being.
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Öffnen Sie | None | T358345 [Epic] Search metrics 2024 | |||
| Resolved | EBernhardson | T370662 Slice Search metrics dashboards by project / language |
I'd like to be able to delineate logged out versus logged in (what is referred to as "editor status" in the parent task) as well. I believe the line charts can stay as is, meaning we don't need to have separate lines based on logged in versus logged out but it would just be nice to be able to click a button or two from the dashboard in order to check the metrics for a particular population. @Gehel any problem if I adjust the Title and Description of the task?
I'll break the editor status request to a different task because it is probably more work.
I think this is working, although it's a bit awkward. Notably the project_class and project columns aren't really linked, so if the user selects wikidata as the project_class they still get 400 project options, even though wikidata has only 2 (or maybe 1, not clear on how test vs prod is represented).
I'm actually not going to bother with filing a new ticket on editor status. We can go for that later if we see a need.