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.

Sign up for GitHub

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

Jump to bottom

Enable per hour time-entry #102

Open
NicholasSloan opened this issue Nov 13, 2020 · 0 comments
Open

Enable per hour time-entry #102

NicholasSloan opened this issue Nov 13, 2020 · 0 comments

Comments

@NicholasSloan
Copy link

NicholasSloan commented Nov 13, 2020 •
edited

Timer works only in minutes and seconds, which is fine, but I'd love to be able to enter times in hours, even if "2h" shows up as 120'. (Otherwise an almost perfect app.) The consistent syntax would be 2:1.30 = 2h, 1m, 30 secs. (Not a realistic timing, just to demonstrate the proposal.)
@NicholasSloan NicholasSloan changed the title Timer works onbly in minutes and seconds, which is fine, but I'd love to be able to *enter* times in hours, even if "2h" shows up as 120'. (Otherwise an almost perfect app.) Timer works onbly in minutes and seconds, which is fine, but I'd love to be able to *enter* times in hours, even if "2h" shows up as 120'. (Otherwise an almost perfect app.) Edit: actually the consistent syntax would be 2:1.30 = 2h, 1m, 30 secs. (Not a realistic timing, just to demonstrate the proposal.) Nov 13, 2020
@NicholasSloan NicholasSloan changed the title Timer works onbly in minutes and seconds, which is fine, but I'd love to be able to *enter* times in hours, even if "2h" shows up as 120'. (Otherwise an almost perfect app.) Edit: actually the consistent syntax would be 2:1.30 = 2h, 1m, 30 secs. (Not a realistic timing, just to demonstrate the proposal.) Enable per hour time-entry Nov 13, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@NicholasSloan