We have implemented our own time tracking utility to overcome a few shortcomings we see.
One of these items is abandoning a currently tracked item. Sometimes I want to change the time being tracked to a different item. With new timetracker, I have to stop tracking, go to monthly view on website, and edit item to shift to required work item.
I have also upvoted another item for adjusting start time. This is another feature we have built into our client.
Our client is currently inserting data directly into the TimetrackerOnlineDb database. Not the best solution, but the API doesn't currently provide the features we want to migrate across to using it.
-
You can start new track by calling startTracking method: http://timehub.7pace.com/apireference/index#/Client/Client_StartTracking
This stops running track and starts new one with new details.
Maxim
-
I would like to throw away the current track, and not record any entries in the database.
A new track would then be started with a different work item id.
Your suggestion of calling StartTracking records DB entry and ends the current track, and then starts a new track with the new id. Not quite what I want.
-
I experience this a lot too. A specific case might help explain:
1. I start work on item "meeting page adds client to navigation menu"
2. Several hours in reviewing my commit, I realize that the work ended up actually being related to "navigation design" item because it wan't the meeting page that really couldn't add the client to menu, it was the menu being incapable of accepting any items from anywhere.
3. To document actual distribution of effort, I go through all time records for that day against "meeting page" and recreate them inside "navigation"
Please sign in to leave a comment.
Comments
3 comments