If I enter a time into the duration field when creating a timetracking, but do not enter the specific times between which it was worked, the duration is not saved. It seems to ignore the duration field value entered, but it does work it out correctly based on the time-begin and time-end entered (if I enter times). If I don't enter times, anything I enter in the duration is not saved.

It used to work that I could enter a duration if I wanted to without specifying times - so at the end of the day I might simply add 2 - 3 hours to three different projects if I worked on them all about the same. If my record-keeping doesn't have to be that accurate it saves a lot of time if I don't have to enter actual times but just the duration.

Is this by design, or a bug? If by design, can I argue that it goes back to how it was before?

Comments

Mark_Watson27’s picture

Mark_Watson27 commented
Status: Active » Needs review

Have you checked the Time Tracking options in /admin/storm/timetracking
You may have to un-check the box to automatically calculate the durations

Can you test this and post back?

JmsCrk’s picture

JmsCrk commented
Status: Needs review » Closed (works as designed)

Great, that fixed it.

Sorry for submitting this as a bug, this must be a new option introduced in this version? I just noticed the changed behaviour and assumed it was a mistake. Oops.

Thanks for your help.

Magnity’s picture

Magnity commented

Added a note to the release notes for 1.24.