# 帮助我们构建全新的 2.0 仪表盘 **URL:** \ **Category:** Feature\ **Created:** [2018年四月30日 17:13 UTC](https://meta.discourse.org/t/help-us-build-the-new-2-0-dashboard/86468 "2018-04-30T17:13:00Z")\ **Posts on this page:** 20\ **Page:** 2
**Author:** ![TheBestPessimist](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/thebestpessimist/32/247704_2.png) [@TheBestPessimist](https://meta.discourse.org/u/TheBestPessimist)\ **Post date:** [2018年五月17日 09:45 UTC](https://meta.discourse.org/t/help-us-build-the-new-2-0-dashboard/86468/163 "2018-05-17T09:45:14Z")
> [@uwe\_keim](#): > > How about adding the _weekday_ to all dates That’s a really nice idea. I modified a lot of date strings to customize not showing YYYY of something else. It would be nice to have it in the dashboard by default. ---
**Author:** ![jerdog](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jerdog/32/122843_2.png) [@jerdog](https://meta.discourse.org/u/jerdog)\ **Post date:** [2018年五月17日 11:51 UTC](https://meta.discourse.org/t/help-us-build-the-new-2-0-dashboard/86468/164 "2018-05-17T11:51:28Z")
Looking good guys! When you drill down to a specific graph, you lose the metric. Below is the **DAU/MAU** graph drilled down from the dashboard - and now we don’t know the number as was displayed on the dashboard graph: ![image](https://global.discourse-cdn.com/meta/original/3X/d/2/d2e3267589b1ac5272ea9b20e9e8707276348ab9.png) Can we get the metric for the graph displayed right next to the graph name? Essentially replicating the tooltip and metric value as on the dashboard ---
**Author:** ![j.jaffeux](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/j.jaffeux/32/60297_2.png) [@j.jaffeux](https://meta.discourse.org/u/j.jaffeux)\ **Post date:** [2018年五月17日 11:52 UTC](https://meta.discourse.org/t/help-us-build-the-new-2-0-dashboard/86468/165 "2018-05-17T11:52:54Z")
Sorry I don’t understand, the tooltip is displayed on the title, and what do you mean by “value” ? ---
**Author:** ![jerdog](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jerdog/32/122843_2.png) [@jerdog](https://meta.discourse.org/u/jerdog)\ **Post date:** [2018年五月17日 12:11 UTC](https://meta.discourse.org/t/help-us-build-the-new-2-0-dashboard/86468/166 "2018-05-17T12:11:48Z")
On the dashboard - the graphs look like this with the tooltip _and_ the value of the metric: ![image](https://global.discourse-cdn.com/meta/original/3X/2/8/289ad4e38a2bc7acbcb3d3f64d5c84c2f39d1e98.png) When you drill down to the graph itself so that you can customise the timetable, you get the following without the tooltip (not _that_ big of a deal) and without the value of the metric (bigger deal) and it’s corresponding hover explanation: ![](https://global.discourse-cdn.com/meta/original/3X/f/f/ff613051bef53bc81da1eeeabe37e7c5bbeb9b24.png) Does that make sense? It would be _extremely_ helpful to have the same info on the customisable report graph as the dashboard graph ---
**Author:** ![j.jaffeux](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/j.jaffeux/32/60297_2.png) [@j.jaffeux](https://meta.discourse.org/u/j.jaffeux)\ **Post date:** [2018年五月17日 12:16 UTC](https://meta.discourse.org/t/help-us-build-the-new-2-0-dashboard/86468/167 "2018-05-17T12:16:12Z")
you have the tooltip, look under DAU/MAU : “No. of members…” Concerning the value, I don’t think we will add it on that screen, but we are probably going to add previous period trend line in the chart in 2.1. ---
**Author:** ![jerdog](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jerdog/32/122843_2.png) [@jerdog](https://meta.discourse.org/u/jerdog)\ **Post date:** [2018年五月17日 12:29 UTC](https://meta.discourse.org/t/help-us-build-the-new-2-0-dashboard/86468/168 "2018-05-17T12:29:57Z")
This doesn’t really help if you have to go export the data and then do a sum function to get the result. It’s a lot of wasted effort when it could be added on that screen since the function is already created for the dashboard summary graphs. ---
**Author:** ![j.jaffeux](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/j.jaffeux/32/60297_2.png) [@j.jaffeux](https://meta.discourse.org/u/j.jaffeux)\ **Post date:** [2018年五月17日 13:17 UTC](https://meta.discourse.org/t/help-us-build-the-new-2-0-dashboard/86468/169 "2018-05-17T13:17:23Z")
No it’s not that simple because this page can show arbitrary ranges, when dashboard page functions are done for yesterday/seven days/thirty days ranges. Also this is not the new dashboard page, so it’s kind of off-topic for now, but not saying we don’t want to improve the single report page and we could maybe add your suggestion. ---
**Author:** ![tobiaseigen](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/tobiaseigen/32/539204_2.png) [@tobiaseigen](https://meta.discourse.org/u/tobiaseigen)\ **Post date:** [2018年五月17日 13:53 UTC](https://meta.discourse.org/t/help-us-build-the-new-2-0-dashboard/86468/170 "2018-05-17T13:53:59Z")
Does DAU/MAU have some sort of target number, showing that DAU/MAU health is good? E.g. should it be above 50% or some such, like net promoter score? If so, it might be nice to add this info to the helper text. Also, DAU/MAU is new to me (and probably to many others) so some sort of link to more details about it might be helpful. Also, should maybe “DAU/MAU” be renamed “Stickiness”? I did a google search, and came across this explanation in a [tech crunch article about facebook apps](https://techcrunch.com/2009/10/29/how-to-measure-the-true-stickiness-and-success-of-a-facebook-app/): > Real retention numbers for other people’s products are notoriously hard to come by, but in Facebook there is good 30 day retention data called the DAU/MAU Ratio – which can also be called Stickiness. This is the ratio of Daily Active Users to Monthly Active Users. For example, a DAU/MAU ratio of 50% would mean that the average user of your app is using it 15 out of 30 days that month. ---
**Author:** ![gerhard](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/gerhard/32/119479_2.png) [@gerhard](https://meta.discourse.org/u/gerhard)\ **Post date:** [2018年五月17日 13:56 UTC](https://meta.discourse.org/t/help-us-build-the-new-2-0-dashboard/86468/172 "2018-05-17T13:56:15Z")
Well, the help text for DAU/MAU says: > No. of members that logged in in the last day divided by no of members that logged in in the last month – returns a % which indicates community ‘stickiness’. Aim for \>30%. ---
**Author:** ![tobiaseigen](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/tobiaseigen/32/539204_2.png) [@tobiaseigen](https://meta.discourse.org/u/tobiaseigen)\ **Post date:** [2018年五月17日 13:58 UTC](https://meta.discourse.org/t/help-us-build-the-new-2-0-dashboard/86468/173 "2018-05-17T13:58:28Z")
hmm… must have been added since yesterday? ![39%20AM](https://global.discourse-cdn.com/meta/original/3X/c/8/c864ef8fad148f06549a59037d564d2426228115.png) ---
**Author:** ![gerhard](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/gerhard/32/119479_2.png) [@gerhard](https://meta.discourse.org/u/gerhard)\ **Post date:** [2018年五月17日 14:02 UTC](https://meta.discourse.org/t/help-us-build-the-new-2-0-dashboard/86468/174 "2018-05-17T14:02:20Z")
Yes, it was. [update description of graph · discourse/discourse@0db0495 · GitHub](https://github.com/discourse/discourse/commit/0db04956d7b4b0bf2629decab448f2dcc86efc76) * * * Shouldn’t lower values for “time to first response” be green instead of red? ![image](https://global.discourse-cdn.com/meta/original/3X/9/b/9ba3d20f2fc4be791cac81f742cfac306b223115.png) ---
**Author:** ![Mittineague](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/mittineague/32/114259_2.png) [@Mittineague](https://meta.discourse.org/u/Mittineague)\ **Post date:** [2018年五月17日 18:57 UTC](https://meta.discourse.org/t/help-us-build-the-new-2-0-dashboard/86468/175 "2018-05-17T18:57:14Z")
Perhaps not as easy as a red vs. green, but might negative Y axes be appropriate for some graphs? ---
**Author:** ![merefield](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/merefield/32/176214_2.png) [@merefield](https://meta.discourse.org/u/merefield)\ **Post date:** [2018年五月17日 19:08 UTC](https://meta.discourse.org/t/help-us-build-the-new-2-0-dashboard/86468/176 "2018-05-17T19:08:00Z")
@Sam I PM’d you earlier with the Chrome Javascript errors that appear ---
**Author:** ![j.jaffeux](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/j.jaffeux/32/60297_2.png) [@j.jaffeux](https://meta.discourse.org/u/j.jaffeux)\ **Post date:** [2018年五月17日 19:08 UTC](https://meta.discourse.org/t/help-us-build-the-new-2-0-dashboard/86468/177 "2018-05-17T19:08:24Z")
can you just post it here please ? ---
**Author:** ![merefield](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/merefield/32/176214_2.png) [@merefield](https://meta.discourse.org/u/merefield)\ **Post date:** [2018年五月17日 19:09 UTC](https://meta.discourse.org/t/help-us-build-the-new-2-0-dashboard/86468/178 "2018-05-17T19:09:14Z")
Sure, it’s crazy long, how best to use markdown to encapsulate? ---
**Author:** ![j.jaffeux](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/j.jaffeux/32/60297_2.png) [@j.jaffeux](https://meta.discourse.org/u/j.jaffeux)\ **Post date:** [2018年五月17日 19:10 UTC](https://meta.discourse.org/t/help-us-build-the-new-2-0-dashboard/86468/179 "2018-05-17T19:10:21Z")
Use a service like pastebin ---
**Author:** ![notriddle](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/notriddle/32/133055_2.png) [@notriddle](https://meta.discourse.org/u/notriddle)\ **Post date:** [2018年五月17日 19:14 UTC](https://meta.discourse.org/t/help-us-build-the-new-2-0-dashboard/86468/180 "2018-05-17T19:14:08Z")
> **Depending on how long it is, you could use a details tag** > > The code looks like this: > > ````markdown > [details="Depending on how long it is, you could use a details tag"] > The code looks like this: > ```markdown > [details="Depending on how long it is, you could use a details tag"] > The code looks like this > [/details] > ``` > [/details] > > ```` ---
**Author:** ![merefield](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/merefield/32/176214_2.png) [@merefield](https://meta.discourse.org/u/merefield)\ **Post date:** [2018年五月17日 19:14 UTC](https://meta.discourse.org/t/help-us-build-the-new-2-0-dashboard/86468/181 "2018-05-17T19:14:35Z")
This was in relation to the graphs that intermittently never appear. When that happens I get something like the following in Chrome dev console (pastebin will expire in 24hr). URL is anonymised. [https://pastebin.com/cTdM8P6M](https://pastebin.com/cTdM8P6M) EDIT: Just upgraded again to [v2.0.0.beta10 +21] and everything loads fine now, seemingly every time? Good stuff! @Sam, tested on both my sites … happy to close this issue for me … am curious to know what the fix was ---
**Author:** ![j.jaffeux](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/j.jaffeux/32/60297_2.png) [@j.jaffeux](https://meta.discourse.org/u/j.jaffeux)\ **Post date:** [2018年五月17日 20:57 UTC](https://meta.discourse.org/t/help-us-build-the-new-2-0-dashboard/86468/182 "2018-05-17T20:57:15Z")
I fixed it my last commit, Time to first response will be a “lower is better” kind of stat. ---
**Author:** ![j.jaffeux](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/j.jaffeux/32/60297_2.png) [@j.jaffeux](https://meta.discourse.org/u/j.jaffeux)\ **Post date:** [2018年五月17日 21:00 UTC](https://meta.discourse.org/t/help-us-build-the-new-2-0-dashboard/86468/183 "2018-05-17T21:00:45Z")
I also refactored and added tests for various computations in reports, if you see anything that doesn’t look correct please let me know. [上一頁](https://meta.discourse.org/t/help-us-build-the-new-2-0-dashboard/86468.md?page=1) [下一頁](https://meta.discourse.org/t/help-us-build-the-new-2-0-dashboard/86468.md?page=3)