jira worklog add¶

• Usage: jira worklog add KEY... [flags]

Add a worklog to one or more issues. Use it when recording time spent from the terminal, with optional Markdown or ADF comments.

Time is parsed with the active profile's workday length for day-based values. Comments pass through the validate-and-encode ADF pipeline before submission.

--dry-run runs local parsing and ADF validation but does not contact Jira. --json-input can supply time, started, and a canonical ADF comment for headless workflows.

Input¶

--json-input <FILE>¶

Read worklog payload from JSON file (canonical for agents)

Accepts a file.

--markdown <MARKDOWN>¶

Worklog comment as Markdown

--markdown-file <FILE>¶

Read the Markdown body from a file; - reads stdin

Accepts a file.

Worklog¶

--started <TIME>¶

Worklog start timestamp

--time-spent <DURATION>¶

Human-readable time spent [example: 2h30m]

Safety¶

--dry-run¶

Preview mutation without submitting

Execution¶

-p --parallelism <N>¶

Maximum concurrent requests (1-16)

Default: 1

Output fields¶

With --output json, the response envelope's data object carries these fields. Run jira schema for the full machine-readable schema.

Examples¶

jira worklog add PROJ-123 --time-spent 2h30m
jira worklog add PROJ-123 --time-spent 1h --markdown "Pairing session" # (1)!
jira worklog add PROJ-123 --time-spent 45m --dry-run # (2)!
jira worklog add PROJ-123 --json-input worklog.json --dry-run --output=json # (3)!

1. Include a Markdown comment in the worklog
2. Preview parsing and ADF validation without contacting Jira
3. Use a JSON payload for headless input