Loading Profile...
Time spent graph tag slices don't work as expected
The 'time spent' chart at the bottom of the dashboard gives confusing graphs when tag slices selected are not disjoint. For example, if two tags have a substantial overlap, it's possible to display more than one hour's time usage in a one hour slot. The paradigm of tags rather than categories implies that it's appropriate to use several, and it would be nice to, for example, see time browsing and how much of that was say 'news'.
This isn't the most natural thing to do with bar graphs, and would mean querying the union of tags from the database, but a simple way of displaying the chart would be to use an intermediate colour for the intersection. (or, showing overlap with a diagonal bar divider might be quite funky, but I can't find any examples of that.)
Thanks, Yjo
This isn't the most natural thing to do with bar graphs, and would mean querying the union of tags from the database, but a simple way of displaying the chart would be to use an intermediate colour for the intersection. (or, showing overlap with a diagonal bar divider might be quite funky, but I can't find any examples of that.)
Thanks, Yjo
1
person has this problem
I have this problem, too!
Tell me when someone solves it.
The more people who report this problem, the more it gets noticed.
The more people who report this problem, the more it gets noticed.
Create a customer community for your own organization
Plans starting at $19/month
-
Inappropriate?That's a good point. This was a feature we really wanted to get out and it's not perfect. I think it is ideal for no-overlap tags (like "work" and "personal") and falls over for any tags with any significant overlap.
The tool that we use for the graphs doesn't allow an low opacity overlay, but we COULD add a "stack" called "tag1/tag2 overlap" that was an orange color (between the yellow and the red). I don't know how painful this would be in terms of load on the server, but we can look into it.
Another quick-and-dirty option is to throw a friendly error message in there saying, "Tag slices are best used for tags with zero overlap". Not ideal, but the zero overlap case seems the best way to use it anyhow.
I’m thankful that we have smart users
The company says
this solves the problem
EMPLOYEE
