Please read the full documentation about accepted inputs for the duration format.
Important:
0
or 00:00
as duration will also stop the entry with a duration of zero secondsend
and duration
field needs to be emptyExported records will be locked to prevent manipulation of cleared data.
The permission edit_exported_timesheet
does allow editing and deletion of these
locked entries nevertheless, which by default is given to users with ROLE_ADMIN
and ROLE_SUPER_ADMIN
.
The export state can be set manually or via the invoice and export screens.
Since version 1.14 you can define whether a timesheet record is billable or not.
Non-billable timesheets are excluded from invoices and budget calculations.
Please read the billable documentation to understand the billable
flag.
The search supports filtering by the fields:
user
(only in team timesheets)daterange
customer
project
activity
tags
state
(running / stopped)Besides these filters, you can query for a free search term, which will be searched in the fields:
description
Additionally, you can filter for custom fields by using a search phrase like location:homeoffice
.
This would find all entries with the custom field location
matching the term homeoffice
.
The search terms will be found within the full value, so searching for office
would find:
I love working in my office
Office
This office is beautiful
Our offices are very noisy
Attention: checkboxes have the values 0
(not checked) and 1
(checked).
You can mix the search term and use multiple meta-field queries:
location:homeoffice hello
- find all entries matching the search term hello
with the custom field location
matching the term homeoffice
location:homeoffice contract:fulltime
- find all entries with the custom field combination: location
matching homeoffice
and contract
matching fulltime
expired:0
finds all items whose expired
checkbox is off
There are also special operators, which can be used in conjunction with custom fields (since Kimai 1.19.1):
empty string (e.g. location:
) will find all entries whose value in the location
field is either empty or not existing~
search term (e.g. location:~
) will find all entries that are missing the custom field (created before the field was created)*
search term (e.g. location:*
) will find all entries that have any value in the location
field (basically the opposite of ~
)