| Info |
|---|
These rules apply to both Manual and Automatic timers. If you think that's not what you want let us know. |
Clockwork uses logged time (automatic or manual) and Working Hours to calculate the Time Spent on an issue. See the examples below.
...
Start time | End time | Reported Jira worklog entries | Explanation | |
|---|---|---|---|---|
1 | Tue, 11am | Wed, 3pm |
Total: 12h | Clockwork assumes the user starts everyday work at 11am and will report 8 hours for Tuesday (full day) and 4 hours for Wednesday (11am → 3pm) |
2 | Tue, 5pm | Wed, 11am |
Total: 2h | Clockwork assumes the user starts everyday work at 11am and leaves the office 8 hours later at 7pm. Clockwork reports two hours for Tuesday (5pm → 7pm) and no hours for Wednesday. |
3 | Wed, 5:45pm | Thu, 9am |
Total: 15h 15m | Clockwork assumes the user starts everyday work at 9am and leaves the office 8 hours later at 5pm. As 5:45pm occurred outside the working hours, Clockwork assumes the user has worked overnight and reports 15 hours 15 minutes total. If the Working Hours duration was increased to 9h on Wednesday, Clockwork would report 15m only (see the explanation for case #2 above) |
4 | Fri, 1pm | Mon, 9am |
Total: 2h | Clockwork assumes the user starts everyday work at 9am and leaves the office 6 hours later (see Working Hours for Friday, which spans for 6h duration) at 3pm. Clockwork reports two hours for Friday (1pm → 3pm) and no hours for Monday. Saturday and Sunday are ignored. These days are inactive in the configured Working Hours. |
...