Skip to content
This repository has been archived by the owner on Jan 7, 2019. It is now read-only.

Time entry not created on TP when creating a non-active task #8

Open
dfibuch opened this issue Jun 30, 2017 · 7 comments
Open

Time entry not created on TP when creating a non-active task #8

dfibuch opened this issue Jun 30, 2017 · 7 comments
Assignees
Labels

Comments

@dfibuch
Copy link
Member

dfibuch commented Jun 30, 2017

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:

image

@dfibuch dfibuch added the bug label Jun 30, 2017
@thyde1
Copy link
Member

thyde1 commented Jun 30, 2017

@dfibuch There is a use case for this:

  1. Do some work on a task (A)
  2. Realise you didn't have your timer running
  3. Log the time in OneTime, and say you are not still doing it but you have not yet finished work on it (Harvest entry is created, but timer is not running)
  4. Do work on task (B)
  5. Resume timer to work some more on task (A).

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.

@petevb
Copy link

petevb commented Jun 30, 2017

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.

@dfibuch
Copy link
Member Author

dfibuch commented Jun 30, 2017

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.

@thyde1
Copy link
Member

thyde1 commented Jun 30, 2017

Or we could change the message so we people aren't confused by what it will do?

@Jameskmonger
Copy link

I think that if we do onetime t start and say that we're not still working on it, it should post the data to TargetProcess - the same as when we type onetime t finish.

@thyde1
Copy link
Member

thyde1 commented Jul 3, 2017

@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"!

@dfibuch
Copy link
Member Author

dfibuch commented Jul 3, 2017

@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.

@petevb petevb self-assigned this Jul 4, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

4 participants