Get your own customer support community

About me

Recent activity

Subscribe to this feed
  • idea

    CGram shared an idea in RescueTime on March 29, 2008 00:46:

    CGram
    Data-entry functionality ?
    I understand and appreciate the value of RT's freedom from data entry - the problem with time managment tools I have looked at to date is that they take too much time !

    While RT cures that ailment, it might be nice to have some functionality that allows RT to function somewhere in-between the two extremes:

    e..g. On some user-defined interval, rescuetime pops up and asks users to allocate the various chunks of time that it has recorded since the last pop-up. The existing tags could be used as defaults, but user could push the individual chunks of time to other tags. I'm thinking something easy like drag and drop of indvidual time chunks from the task list to the tag list ( or vice versa). If all of the defaults are OK , then there is nothing to do and user could just confirm and close it.The intra-day pop-up theoretically saves people from having to try to remember a lof of details for too long throughout the day.

    I'm thinking of a case where I get in and out of excel 3 times in a hour or perhaps hits on a frequently used site like Google. Rather than have total time dumped into the same tag e.g. "work", I could see each block of time and push each chunk to the tag I want it to go. If i wasn't sure, it could all just go to "work" , but if I knew for sure that some of it was "personal" I could re-tag one or more of the time blocks on the fly. Obviously there would potentially be a lot of granular data to track for this (or then again maybe you are saving it already).

    Thanks
  • question

    CGram asked a question in RescueTime on March 29, 2008 00:29:

    CGram
    Multi-level tagging
    I am new to RT so maybe I am missing something, but a single layer tag list complicates the reporting a bit (double counting of time?)? I know there are a few ideas floating out there on this board that somewhat touch on this topic, but I didn't see any that quite dial it in like I am thinking...

    It might be cleaner to have say a 3 layer deep tag scheme - e.g. A top layer of "work", a second, middle layer of "admin", and a third, sub- layer of "time management." When someone creates a tag, they specify whether its level 1 2 or 3. A 2 must be assigned to a 1 and a 3 must be assigned to a 2. Then people could choose to look at summaries at level 1, 2 ,or 3. Personally I would fund this more helpful than the currently offerred and more flexible approach of assigning multiple tags. In this scheme user would assign a level3 tag.

    Perhaps a simpler approach to it would be to combine the current flat file list of tags combined with 3 tag fields for each site/app, and these fields control the hierarchy. This gives more flexibility - user could assign whatever tag they wanted at any of the 3 levels - but allows for cleaner more understandable summaries as the user can choose to view the summary based on the tags assigned at either level 1,2 , or 3.

    Thanks, and keep up the good work !