Clockify: "Missing or incomplete field values"

Clockify can refuse an import when a field your workspace requires is empty in some rows. Project is required by default when Timesheet view is on. In the ClientHours Clockify file, events with no client have an empty Project, and the page warns you how many there are, so give those events a client or leave them out first.

What Clockify's help page says

Even if all required fields are present, your import can still fail if some fields are left empty in your CSV file.

Check if Timesheet view is enabled. If it is, Project becomes a required field by default

If any of these required fields are empty in your CSV, the import will not succeed.

Quoted word for word from Clockify's help page, listed under Sources.

Why it happens

  • Timesheet view is on in your workspace, so Project is required, and some rows have no project.
  • Your workspace marks Description, Task or Tag as required, and the file has empty values or no such column.
  • Your workspace requires custom fields that the file does not have.

How to fix it

  1. In Clockify, click the three dots next to your workspace name, select Workspace settings, then Time tracking. See whether Timesheet view is on, and which fields are listed under Time entry required fields.
  2. In ClientHours, add keyword rows until "(no client)" holds only events you do not want in Clockify. Then narrow the dates, or delete those events from the calendar export, so no row has an empty Project.
  3. If your workspace requires Task or Tag, Clockify's page suggests turning the required fields off for the import and back on afterwards. The ClientHours file has no Task or Tag column.
  4. Click "Clockify import (CSV)" and import the new file.

Calendar to Clockify CSV import

What the ClientHours file does

  • Project and Client are both filled with the client from your keyword table, because a calendar has no projects.
  • Rows with no client have an empty Project and Client. The page counts them and warns before you import.
  • Description is the event title. An event with no title has "(no title)".
  • Start date, Start time and Duration are filled on every row. Email holds the Clockify email you type, or your own address from the page if you leave it empty. If both are empty, Email is empty on every row and the page warns you, so enter one before you download.

Limits

  • The file has no Task, Tag, Billable or custom field columns. A workspace that requires any of them needs that requirement turned off for the import, or the columns added by hand.
  • Clockify's troubleshooting page lists Task, Tag and User among required headers, while its main import page lists Task and Tag as optional. The file follows the main import page.
  • Clockify's import page lists timesheet import as available on any paid plan.
  • No ClientHours file has been tested by importing into a real Clockify account. What the file contains is checked by tests. How Clockify reads it comes only from the help pages under Sources.

Questions

Why is Project empty on some rows?
Those events matched no keyword in your client table, so they have no client, and Project repeats the client. Add a keyword row for them or leave them out.
Do I have to turn Timesheet view off?
No. Clockify's page says Timesheet view makes Project required by default. If every row has a project, the requirement is met.
Does the file include Task or Tag?
No. A calendar has no tasks or tags. If your workspace requires them, Clockify's page suggests turning required fields off during the import.

Sources

Other import problems

ClientHours is free, with no account and no payment. The calendar file never leaves your browser.