After scaffolding the UserCountGraph component in #2392, it should now actually be implemented.
_Do not alter or remove anything below. The following sections will be managed by moderators only._
UserCountGraph component for the Analytics DashboardAllTrafficWidgetV2 should be fully implemented:ga:users, the dimension ga:date, dates based on the current date range, and optionally the current entity URL, if there is one.dimensionName and dimensionValue props are present, it should also consider those for querying the report, as dimensionFilters.DashboardAllTrafficWidgetV2 should have its setup updated, to populate the registry with corresponding test report data, so that the UI rendered by UserCountGraph is visible there.GoogleChart component:AreaChart chart when the chartType property equals to area.UserCountGraph component:useSelect hooks which do the following:startDate/endDate dates from the core/user datastore using the getDateRangeDates selector;url from the core/site datastore using the getCurrentEntityURL selector;module/analytics datastore using the getReport selector with ga:users metrics, selected dimension name and value (if it's not empty), startDate/endDate dates and url received from the aforementioned selectors;GoogleChart component to display the chart. Check AnalyticsDashboardWidgetSiteStats as an example to see how we use this component and the AreaChart documentation for more details on how to configure it.DashboardAllTrafficWidgetV2 component to properly configure the UserCountGraph component.UserCountGraph component for new Analytics All Traffic widget.I'm not sure the IB here is specific enough, because from what I've seen in the Google Charts docs for LineChart, there's no way to have the area below the line filled in, as in the mocks:

In order to have the area under the line filled in we'd need to use a separate chart, the AreaChart. We should still be able to use curveType to achieve the curve effect I think.
Because we'd need to use a new kind of chart and it'd be fairly different from existing ones, I think this might need a bigger estimate as well, but I think for this one we should be a bit more particular about the IB. The general sense of the IB is good, but I think needs more specificity on how they chart will be made.
Good catch, @tofumatt! I didn't notice it at the beginning, thank you! I have updated the IB to outline that we need to add a new chart type to make it work.
IB โ
No need for you both to review, but I thought I'd assign it to both as I know this is high-priority ๐
The new All Traffic widget appears on SK Dashboard - Screenshot
The chart with the total number of users is shown and changes when you change the active tab in the widget.
@tofumatt this passed the QAB but have a few observations that I wondered if we could look at (I can create new tickets) 1) Sometimes, the users, pie chart and graphs load slow (feels like 5-10 seconds) when you have selected a slice and a date period. I guess this could be a limitation with the API, but, thought I would highlight. 2) On mobile you do not always see the data in the right axis, not a huge issue since I doubt many will use mobile in the dashboard, but thought I'd flag it. - Screenshot
Sometimes, the users, pie chart and graphs load slow (feels like 5-10 seconds) when you have selected a slice and a date period. I guess this could be a limitation with the API, but, thought I would highlight.
Yeah, that's just a slow API request. I noticed it too; maybe that particular request is slow. But I think it's "expected" behaviour for now.
On mobile you do not always see the data in the right axis, not a huge issue since I doubt many will use mobile in the dashboard, but thought I'd flag it.
Yes, I caught that too. The Figma mocks don't have explicit mobile mocks and several of these components could use further mobile optimisations. Can you open a follow-up issue to improve the whole widget area on mobile viewports referencing that right axis issue in particular? ๐
I think this belongs in Approval for now though, yeah ๐๐ป