I suggest you ...

optionally allow the default to be productive time and the exception list to be non-productive time

flip the default/exception behavior so that any time is presumed to be productive unless one of the configs (app, keyword) matches, in which case it is unproductive.

6 votes
Vote 0 votes Vote Vote
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    I agree to the terms of service

    You'll receive a confirmation email with a link to create a password (optional).

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Clark WilsonClark Wilson shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

    1 comment

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      I agree to the terms of service

      You'll receive a confirmation email with a link to create a password (optional).

      Signed in as (Sign out)
      Submitting...
      • Simon CelenSimon Celen commented  ·   ·  Flag as inappropriate

        It might be interesting to be able to define custom timeframes. In addition to having (un)productive, you could have "client work", "design", "coding", etc.

      Knowledge Base and Helpdesk