Store individual time sessions instead of only summed values #69
vis-joel
started this conversation in
Feature request / Ideas
Replies: 1 comment 1 reply
-
|
Thank you for your request. I've thought about that too, and I think it would be a good idea to store every session. That could also serve as the foundation for further features. I'm not sure if I should include this in version 2.0.0. I hadn't actually planned on adding any new “features.” But maybe it would make sense to include it after all, since it could require some big internal changes. Otherwise, I'll add it to the next feature release v2.1.0. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
🤔 Problem to solve
First of all, I really like the extension, and the current v2 preview looks great.
One thing I noticed: currently, time entries seem to be stored as a single summed value in localStorage. This works fine in general, but becomes tricky when I forget to stop a timer, since I then have to estimate afterwards when I last interacted with it.
💡 Proposed solution
Would it be possible to store each start/stop as a separate session (similar to Clockify)?
Idea:
This would make it much easier to review and correct time entries if a timer was left running.
Not sure how big of a change this would be for v2, but I thought I’d share the idea and maybe it can help in the future solving other problems 🙂
📎 Additional context
No response
Beta Was this translation helpful? Give feedback.
All reactions