Tag: time entry

Categories
Release Notes

ClickTime Version 10.28.0

  • Added a new company preference to hide the Quick Day and Quick Week views within Time Entry.
  • REST API: Added the “HideQuickDayWeek” property to the GET and PATCH /Company endpoints for setting the company preference.
  • Fixed a broken help link on the admin user deactivation page.
Categories
Release Notes

ClickTime Version 10.25.0

  • The Advanced page has been redesigned with an updated look and feel
  • Mileage Reimbursement Rate: The mileage reimbursement rate for 2026 was updated
  • Fixed an unexpected error that prevented time entry in certain scenarios

Categories
Expenses Release Notes

ClickTime Version 10.18.0

ClickTime Version 10.18.0 includes the following updates:

Approval Dashboard:

  • Banner text was updated to reflect the name “Approvals Dashboard”
  • The Help Link for the page was updated

The following issues were resolved:

  • Time Off and not loading for certain users
  • “Waiting for your Approval” message shows to admin that does not approve locked links
  • Clearing Job Approvals filter does not reset it
  • Filters not recognizing when moving from one to all
  • Wrong approver appearing in timesheet details modal
  • Project Approvals tab not loading

Time Entry:

The following issues were resolved:

  • Using a stopwatch causes an expired stopwatch notification
  • Unexpected error occurs when adding a time entry
  • Last viewed time entry page not setting as default when logging in

Expenses:

When creating a new expense sheet, the modal opens with a validation error. This issue is now resolved.

Categories
Release Notes Time Tracking

ClickTime Version 10.12.0

ClickTime Version 10.12.0 includes the following updates:

Report Studio: An issue with Subscription and Excel exports not working as expected was resolved.

Time Entry: The following bug fixes and improvements were made to our time entry pages:

  • Auto Fill deletion warning said “week” when using Day View
  • Autofill Deletion warning could not be dismissed on Day View and Week View
  • Admin receives “Unexpected Error” and cannot remove (approval required) PTO from employee’s timesheet
  • Deleting the hours on Week View with autofill clears the row
  • Quick Week was not carrying Time Off forward into new periods

REST API: The following issues were resolved:

  • IsActive=false was returned for PaymentType and ExpenseType in GET /expenseItems/new?verbose response
  • Leading and trailing white spaces are not trimmed on POST /ExpenseTypes
  • Documentation for POST /Timesheets/{id}/Actions and /Timesheet/Actions was updated to clarify the limited set of actions managers with “Override Timesheets” permissions can perform.

The following endpoints are now public:

  • GET /Users/{userID}/ExpectedWork
  • POST /Users/{userID}/ExpectedWork
  • GET /Users/{userID}/ExpectedWork/{expectedWorkID}
Categories
Release Notes Resource Management Time Tracking

ClickTime Version 10.08.0

ClickTime Version 10.08.0 includes the following updates:

Time Entry: The following issues have been resolved:

  • Users being auto-navigated to (yesterday’s) date instead of current date when logging in
  • Day and Week View pages not loading for certain users due to bad timer data

Automated Notifications: Some automated notifications failed to send after Daylight savings. This issue is now resolved.

Bug Fixes: The following issues were resolved:

  • Audit Log not capturing changes made to a user’s email address
  • Resource Management Grid tabs not opening Dashboard
  • 500 error when clicking the “Full Report” button on the Billable Hours Company Dashboard panel

Categories
Release Notes

ClickTime Version 10.04.0

ClickTime Version 10.04.0 includes the following updates:

REST API: The following REST API issues were resolved:

  • POST a mileage expense type without rate value
  • 500 error appearing on Reports/ManagedTimesheets if sorting by end date
  • ExpectedWork endpoint ignoring UserID in URL

Time Entry: There was an issue on Day View where searching for a ‘+’ would log the user out. This issue is now resolved.