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

If an entry occurs multiple times, then which one does "continue" use? #16

Closed
drobertadams opened this issue Nov 3, 2014 · 3 comments
Closed

If an entry occurs multiple times, then which one does "continue" use? #16

drobertadams opened this issue Nov 3, 2014 · 3 comments

Comments

@drobertadams
Copy link
Collaborator

Good question!
@beauraines
Copy link
Contributor

I don't use the continue function, because I like to see the task switching and how long I spend uninterrupted. But as a non-user of the function, I'd think it would continue the "last" entry.

I'm also leaning that way, because I think I'd like a 'start the last entry again' function. This way I don't have to retype the time entry description the same way. So a function that identifies the last entry could be used for both the continue function and this new startlast

My two cents.

@drobertadams
Copy link
Collaborator Author

Actually, I answered my own question. I believe the code will restart the latest entry (or at least the last one as returned by toggl; I'm not sure they are returned in time-sorted order), so it should be relatively easy to refactor that into "restart the last entry" option.

@drobertadams
Copy link
Collaborator Author

Definitely fixed now. The new TimeEntryList object sorts by start date.

devkev pushed a commit to devkev/toggl-cli that referenced this issue Sep 7, 2016
@beauraines
Fixes AuHau#16 - time entry with start time ignored
b6e9da0 
1) Switched from the start endoing time_entries/start to the create end point time_entries. Start always used the current time and the create endpoint needs a start time specified.
2) This meant that the create_time_entry code needed to create a current time in the localized timezone as well as,
3) The parsed time argument to be put into a localized time string as well.

Much thanks to Margus at Toggl for pointing out the differences between the end points to me.
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
2 participants
@drobertadams @beauraines