Skip to main content
Skip table of contents

How time spent is calculated (legacy mode)?

Clockwork uses logged time (automatic or manual) and Working Hours to calculate the Time Spent on an issue. See the examples below.

When the Timer Starts and Stops on the Same Day

When all work is logged on the same day, Clockwork will take the time between a start and stop without taking Working Hours into account. Because Working Hours are not considered, a user can log more than 8 hours in a single day.

Start time

End time

Calculated hours

Monday 9am

Monday 4pm

7h

Tuesday 7am

Tuesday 4:50pm

9h 50m

When the Timer Starts and Stops on Different Days

In cases where the timer starts and stops on different days, Clockwork uses Working Hours to calculate the Time Spent. This ensures accurate time tracking without users needing to remember to start and stop timers at the beginning/end of their workdays.

Time reported in a different time zone will be converted to the time zone from the Clockwork configuration.

The following examples assume that the time zone is set to UTC and that the working hours are as follows:

While Working Hours shows a specific start and end time, Clockwork recognizes that different users have different schedules. (A user can configure their own Working Hours, by going to Apps > Clockwork in the main Jira menu and selecting Working Hours). Clockwork will assume the user’s normal start time based log entries and use the number of hours allowable in a work day (from the Working Hours) to detects overnight and over-the-weekend time. The overnight and over-the-weekend time will be subtracted from the total time logged to calculate the Time Spent. The total reported time will be split among days worked with one Jira worklog entry for each day.

Examples

Start time

End time

Reported Jira worklog entries

Explanation

1

Tue, 11am

Wed, 3pm

  • 8h for Tue

  • 4h for Wed

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 (11am3pm

2

Tue, 5pm

Wed, 11am

  • 2h for Tue

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

  • 6h 15m for Wed

  • 9h for Thu

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

  • 2h for Fri

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 15pmClockwork 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.

Multiple Issues In Progress

Clockwork only allows a user to log work on one issue at a time. If a user has a time running on more than one issue, they will see a warning prompting them to transition (or reassign) one of the issues.


JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.