We saw that this will be a source for confusion so we decided to introduce the notion of "bulk entry" (which you are already a bit familiar with from my timesheets page).

Internally it will be just as a normal entry with start/stop but when displaying entries like this, the user will see only the amount ( 5 hours for example ) instead of a start-stop time since anyway the start-stop does not reflect the reality nor is it important to the user. PaymoPlus application is adding these types of entries it's just that we did not update our backend yet to not display the start-stop for them.


You are right about the fact that entries in the backend are not exactly as items in PaymoPlus but here is the dilemma.

consider the following examples (A,B,C)


Suppose that "Window A" and "Window B" are related to Task 1

and "Window C" and "Window D" are related to Task 2





In #A, we create a separate entry for each time a window is in foreground. In this case the start-stop for each entry will be exact, however we noticed that usually a window is focused just for a few minutes then the user switches to another one. This would lead to application creating hundreds of entries per day which would make the backend unmanageable.


In #B we create a single entry for each task and the duration of the entry is equal to the sum of durations for windows that relate to that task.

As you see the time-frame of each entry does not reflect the reality ( although the duration is exact, and this is what counts in the end ) but in this case we have only one entry per task per day.


In #C (it's the same as #B) notice the order of windows this time is ABCD, i.e. the user worked on Task 1 then he worked on Task 2. In this case we also have 2 entries and their time-frame reflects the reality.


Ideally, a user should follow case #C and everything will be exact, however the pattern we see most of the time is that a user will work on task 1 then go to task 2 then come back to task 1 and so on and so on.


When implementing the application we had to choose from #A and #B and it quickly became clear that #B is the only way to do this.

understood, and already gave up about paymo plus anyways.

tried things like this years ago yet, but it plain can't work. i thought i'd give it a try as having the entries going directly to paymo might be cool, but it's just making things too complicated.


besides, without having real timestamps it's useless to me, as paymo for me also is some kind of logbook, a way to know and remember *when* i did what and sometimes even *where* - so if there is an entry at 11am of work i actually did at 10pm it just creates a mess..

PaymoPlus is not for everyone, that's why we took the timer approach from start. It can work for some people though. Thanks for trying it out!

Are there plans to make this more accurate from a freelance computer cloud agent.... I need to be able to bill on the fly with accurate time stamps... What is the best way to log data..

There are no plans to change the behavior of this application. If you need accurate timestamps use the default desktop client and the start/stop functionality

You guys sound angry like you don't want to work on Paymo anymore.. It is close but needs little updates. Why would you want to push people away??

No one is angry Jeff :), this app however is not designed for people who care about timestamps.