Keep your ledger moving.

Open Timers and press Start timer. The timer begins immediately. If you want to enter a description and tags first, choose Add details before starting instead.

Yes. Start another timer while one is active. Each timer remains independent and continues across app restarts until you stop it.

Tags use a key:value structure—for example project:zero. Choose an existing tag name and value, or press New to create one. A single time entry can only contain one value for each tag name.

Yes. Open a recent entry to edit its start time, end time, description, tags, and optional position. You can also delete the entry.

Open Summary, choose days or weeks, then filter by one or more tags. This makes it easy to isolate work for a customer or project before exporting it.

Wait for the export to finish, then try again with ClockLedger in the foreground. If necessary, close and reopen the app. An export is only written when you request it.

iOS normally removes the app’s local database with the app. Keep a recent SQLite export before deleting ClockLedger or erasing the device.

Add a Jira connection in Settings, import issues, and use the configured tag name on a completed entry. In Summary, use Sync worklogs to Jira for that tag. ClockLedger keeps the Jira worklog identifier for later updates and writes a hidden ClockLedger entry marker into the worklog comment.

Confirm the Jira account can browse the project and add worklogs to the issue. Also check that the entry has a positive duration and that the tag value is a valid issue key. Jira Cloud usually uses an account email plus API token unless OAuth has been configured.

It sends selected completed entries to the self-hosted Traggo server you configure. Export is one-way: ClockLedger does not import, replace, or delete Traggo data.

ClockLedger can allow a server without HTTPS after warning you. HTTP exposes credentials and time records to the network, so HTTPS is strongly recommended.