| Info |
|---|
Manual and automatic modes use the same configuration and algorithm for work time calculation. |
...
You can set the number of working hours per day and working days in plugin configuration (see Configure General and project settings for Automated Log Work Cloud).
| Info |
|---|
Default setting for working hours per day is 8 hours. Default settings for working days are Monday, Tuesday, Wednesday, Thursday and Friday. |
...
Time logged does not depend on exact business hours what is explained in examples.
| Info |
|---|
Running timer means that user pressed "Start Timer" button in Manual mode or moved issue to active status (e.g. "In Progress") in Automated mode. |
...
In "different days" scenario our smart algorithm detects overnight and over-the-weekend work and skips redundant time to log only real working hours, e.g.:
- Timer starts at 1pm one day and stops at 9am next day - "4h" is saved to JIRA worklog
- Timer starts at 5pm one day and stops at 11am next day - "2h" is saved to JIRA worklog
- Timer starts at 5:45pm one day and stops 9am next day.
Let's explain the second example:
Because the start/stop timer events happened in different days, it means there was "overnight" time tracked and we definitely don't want to save it to JIRA worklog so our smart calculation starts.
...
Let's explain the third example:
Time difference between 9am and 5:45pm is 8:45 hours and it is longer than 8 hours specified in working hours per day configuration option. Therefore our algorithm is not able to tell if and when user left the office.
In such case we assume that user worked throughout the night and time calculated from 5:45pm to 9am next day is 15 hours and 15 minutes (it is equal to 8h + 7h + 15m = 1d 7h 15m).
If we increase working hours per day value and set it to 9h then we get 15m as an outcome of our algorithm that is saved to JIRA worklog.
...
Working business hours
Several customers requested a configuration option to specify precise hours when users come to office and next leave the office.
We want to explain that such option would not improve accuracy of time tracking but make it worse.
As explained in the previous paragraph, our algorithm works fine despite of actual time when user enters and next leaves the office. The only conditions that must be satisfied are:
- User works as long as defined in configuration (working hours per day and working days)
- User starts and ends work at the same time on the first and last day (timer might work for several days or weeks)
The proposed "enter/leave office hours" solution is even more strict as it requires following to work correctly:
- User works as long as defined in configuration but also in specified hours (e.g. between 7am and 3pm).
In our original algorithm it is enough if users works 8 hours, it might be 7am-3pm or 9am-5pm so it is more flexible. - User by definition starts and ends work at the same time on the first and last day of work (when timer works for several days or weeks)
This assumption is exactly the same as in our original algorithm.
Overall, our working time calculation algorithm is less strict and therefore more precise in its current shape. Adding precise hours when user enters and leaves the office would make it less accurate.
...