-
Notifications
You must be signed in to change notification settings - Fork 1
Time entry not created on TP when creating a non-active task #8
Comments
@dfibuch There is a use case for this:
If OneTime were to finish the timer on task (A) (and immediately log the time to TP) as soon as you say you're not working on it now, you would not be able to resume your timer on that task. |
So, "are you still working on it" really means, "shall I start a timer". I agree that's not particularly intuitive @dfibuch but it's probably by design. |
Ye I can see cases for both of these but it just reinforces my point about onetime time logging taking so long because to log a single entry I not only need to fill out a survey to make a timer I then need to fire off another command to finish it. I guess it is by design but as Pete said not intuitive. I guess we can close it down. |
Or we could change the message so we people aren't confused by what it will do? |
I think that if we do |
@Jameskmonger Again, I think what we need to look at is the wording of the message. I think that behaviour you're describing should happen if the message was "Is this task finished"... or be even more clear "Do you wish for this timer to not be running and log to TP now"! |
@Jameskmonger That's where my confusion came from, it's what I assumed it would do. If we are to cover off @thyde1's scenario above, if you want to log more time to Task A just start another timer. |
I'd expect that when doing
onetime t start
, specify how many hours I've worked on a task and then answer "No" to the "Are you still doing this?" question it would automatically log that to Target Process as well as creating the entry in Harvest (which it does). It's essentially creating a finished task so why would we have to finish it again to log it?Example entry:
The text was updated successfully, but these errors were encountered: