Skip to content

odoo-work-cli entries

NAME

odoo-work-cli-entries - List individual timesheet entries with full detail

SYNOPSIS

odoo-work-cli entries [--week YYYY-Www | --date YYYY-MM-DD] [--project TEXT] [--task TEXT] [--status STATUS] [--json | --format FORMAT]
odoo-work-cli entries add|update|delete [OPTIONS]

DESCRIPTION

List your timesheet entries of an ISO week (--week, default the current week) or of one day (--date, which takes precedence over --week), with the validation status of each entry and the total.

--project and --task keep the entries whose project or task name contains the text, ignoring case; --status keeps the entries with exactly that validation status (draft or validated). The filters combine. The [models.timesheet] filters of the configuration apply as well.

The subcommands add, update and delete write entries.

Subcommands:

odoo-work-cli entries add
Create a new timesheet entry.
odoo-work-cli entries delete
Delete a timesheet entry.
odoo-work-cli entries update
Update an existing timesheet entry.

OPTIONS

--date YYYY-MM-DD

Single day to list, YYYY-MM-DD; overrides --week.

string; optional

--project TEXT

Only entries whose project name contains TEXT (case-insensitive).

string; optional

--status STATUS

Only entries with validation STATUS draft or validated.

string; optional

--task TEXT

Only entries whose task name contains TEXT (case-insensitive).

string; optional

--week YYYY-Www

ISO week to list, YYYY-Www (e.g. 2026-W10).

string; optional; default: the current week

GLOBAL OPTIONS

--format FORMAT

Output FORMAT: table, json or jsonl.

one of table, json, jsonl; optional; default: table

--json

Shorthand for --format json.

flag; optional

--backend BACKEND

BACKEND: odoo or fake (offline, made-up data; env ODOO_WORK_CLI_BACKEND).

string; optional; default: odoo; env: ODOO_WORK_CLI_BACKEND

--config FILE

Read only the config FILE (skip discovery).

string; optional

-h, --help
Print the help of the command and exit.

OUTPUT

A "Week: FROM to TO" or "Date: DAY" line, then the columns ID, Date, ProjID, Project, TaskID, Task, Hours (H:MM), Status and Description, then the total and the number of entries.

With --json the output is an array of entries, [] if none match.

Fields of entry.schema.json:

id
integer
date
string (YYYY-MM-DD)
project_id
integer or null
project
string or null
task_id
integer or null
task
string or null
description
string
hours
number
minutes
integer
employee
string or null
status
string or null
company
string or null

ENVIRONMENT

ODOO_URL
Odoo server URL; overrides url from the config files.
ODOO_DATABASE
Odoo database name; overrides database.
ODOO_USERNAME
Odoo login, usually an e-mail address; overrides username.
ODOO_PASSWORD
Odoo API key, used for XML-RPC. Despite the name, not the login password.
ODOO_WEB_PASSWORD
Odoo login password, used for the web session of clock in and clock out.
ODOO_TOTP_SECRET
TOTP secret (base32 or otpauth:// URL) for accounts with two-factor authentication.
ODOO_OP_TIMEOUT
Timeout of the 1Password call that resolves [op_secrets], a Go duration; default 5s.
ODOO_WORK_CLI_NO_OP
If 1, true, yes or on, [op_secrets] is ignored and the 1Password CLI is never called.
ODOO_WORK_CLI_BACKEND
Backend, odoo (default) or fake; --backend overrides it.
ODOO_WORK_CLI_FAKE_STATE
State file of the fake backend; default odoo-work-cli-fake-state.json in the temporary directory.
XDG_CONFIG_HOME
Base directory of the global config file; default ~/.config.

FILES

~/.config/odoo-work-cli/config.toml
Global configuration ($XDG_CONFIG_HOME/odoo-work-cli/config.toml if XDG_CONFIG_HOME is set). Created by odoo-work-cli config install.
.odoo-work-cli.toml
Configuration of a directory tree. Every such file from the filesystem root down to the current directory is merged over the global file, the deepest last. --config FILE loads only FILE instead.
$TMPDIR/odoo-work-cli-fake-state.json
State of the fake backend (--backend fake); ODOO_WORK_CLI_FAKE_STATE sets another path. Delete it to start over with the seed data.

EXIT STATUS

0 on success, 1 on any error, including usage errors. With --json or --format json|jsonl the error is printed on standard output as one JSON object, {"error": {"kind": KIND, "message": TEXT}}, and nothing on standard error; otherwise as "Error: TEXT" on standard error, after usage errors followed by the usage.

Error kinds this command can fail with:

auth
Authentication failed: wrong API key or login password, TOTP rejected.
validation
Invalid input: unknown flag, bad argument, malformed date, time or hours, a time in the future, an unknown project.
network
Odoo cannot be reached: DNS, connection refused, timeout, TLS.
config
The local configuration is missing or invalid.
secrets_locked
1Password is locked or unreachable, so op:// references could not be resolved.
internal
Anything else: an unexpected Odoo response or a bug.

EXAMPLES

The entries of one day:

$ odoo-work-cli entries --date 2026-04-08
Date: 2026-04-08

ID       Date         ProjID   Project                   TaskID   Task                      Hours  Status     Description
-------- ------------ -------- ------------------------- -------- ------------------------- ------ ---------- ------------------------------
4016     2026-04-08   3        Internal                  32       Training                  1:30   draft      Accessibility workshop
4015     2026-04-08   2        Orchard Mobile App        22       Support                   2:30   draft      Crash report on login
4014     2026-04-08   1        Lighthouse Portal         12       Frontend                  4:00   draft      Result list layout

Total: 8:00 (3 entries)

The draft entries of a week on projects named like "portal", as JSON:

$ odoo-work-cli entries --week 2026-W15 --project portal --status draft --json
[
  {
    "id": 4018,
    "date": "2026-04-09",
    "project_id": 1,
    "project": "Lighthouse Portal",
    "task_id": 13,
    "task": "Code review",
    "description": "Review fuzzy matching",
    "hours": 1.5,
    "minutes": 90,
    "employee": "Alex Demo",
    "status": "draft",
    "company": "Example Consulting"
  },
  {
    "id": 4014,
    "date": "2026-04-08",
    "project_id": 1,
    "project": "Lighthouse Portal",
    "task_id": 12,
    "task": "Frontend",
    "description": "Result list layout",
    "hours": 4,
    "minutes": 240,
    "employee": "Alex Demo",
    "status": "draft",
    "company": "Example Consulting"
  },
  {
    "id": 4011,
    "date": "2026-04-07",
    "project_id": 1,
    "project": "Lighthouse Portal",
    "task_id": 11,
    "task": "Backend API",
    "description": "Search: fuzzy matching",
    "hours": 3.5,
    "minutes": 210,
    "employee": "Alex Demo",
    "status": "draft",
    "company": "Example Consulting"
  }
]

SEE ALSO