Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Log interrupted / uncompleted tomatoes along with reasons. #106

Open
carlwilson opened this issue Oct 17, 2013 · 5 comments
Open

Log interrupted / uncompleted tomatoes along with reasons. #106

carlwilson opened this issue Oct 17, 2013 · 5 comments
Labels

Comments

@carlwilson
Copy link

Three reasons:

  • Leaves an audit trail of the "lost" / non productive hours.
  • Useful for review, work out when and why interruptions occur.
  • The original PT literature suggests logging interruptions.

To be fair the literature also distinguishes internal and external interruptions, but the ability to tag interruptions would be more flexible.

@klamping
Copy link

👍

@deilann
Copy link

deilann commented Mar 15, 2014

👍

Also, often my last pomo is incomplete-- because my project is done. That's time that still needs to be logged.

@LeBaux
Copy link

LeBaux commented Mar 18, 2014

Very much needed. Please.

@potomak
Copy link
Member

potomak commented Jan 22, 2017

This feature would work well in conjunction with #219.

@carlwilson @klamping @deilann @LeBaux still interested?

@carlwilson
Copy link
Author

I'll vote yes for still interested 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants