google-calendar-hours icon indicating copy to clipboard operation
google-calendar-hours copied to clipboard

IDEA: Summarize hours based on hashtags

Open mayurjobanputra opened this issue 3 years ago • 2 comments

I love what you can do with this app. What I would love to be able to do is use my own tags so that I can use tags to summarize the week or month (hashtags maybe?). Why? I want to be able to quickly summarize efforts across the multiple projects and meetings I have going on. The ability to use multiple hashtags would be great.

Eg:

Calendar item xxx: #clientABC #meetings Calendar item yyy: #clientABC #webdevelopment Calendar item zzz: #webdevelopment #personalsite Calendar item aaa: #workingout

User story:

As a user, I want to see a summary of my activity based on my own custom keyword(s) so that I can easily summarize how much time I spend on certain activities

TDD/BDD Scenarios (shortened form - if you want me to elaborate I can):

One or more calendar items have no hashtags: show as uncategorized One or more calendar items has one hashtag: total and summarize all that match One or more calendar items have multiple hashtags: show in a multi-level tree with totals

Having written the scenarios above, one realization I'm having is from the third scenario: if a user uses multiple hashtags in a calendar entry, then doing summaries becomes an issue because totals can overlap and not be broken down my client/project/hashtag. So might need to use a tree where the depth of the tree is determined by the number of hashtags so that users can drill down (client > task > etc). This poses a new problem though: what hashtag should be the "top of the tree"? I guess you would start with most hours at the top, and then each branch is the next "most hours" for that hashtag. Hope that made sense?

mayurjobanputra avatar Feb 10 '22 01:02 mayurjobanputra

Something similar mentioned here: https://github.com/aronwoost/google-calendar-hours/issues/158

mayurjobanputra avatar Feb 10 '22 01:02 mayurjobanputra

Not sure what happened earlier (closing issue). Re-opening for comments

mayurjobanputra avatar Feb 10 '22 08:02 mayurjobanputra