A correction is how closed time gets changed. Because a closed period freezes every time entry in it, you never edit the original; instead an Owner or Admin adds a correction: a new entry with a signed number of minutes (negative to take time away, positive to add) that points at the original. The original stays exactly as it was, and the history shows both. In the weekly grid and in reports a correction is labelled "Adjustment".
How it relates to other concepts
- A correction is dated today, in the actor's time zone, and lands in today's open period. That is why reports say adjustments appear in the period they were made.
- A billing run bills a correction in the period it was made, marked as a correction on the run and on the client timesheet. A correction of an original that has not been billed yet waits for the original.
- Deleting a ticket is refused while any of its time is in a closed period, so corrections are also the answer when a closed entry was logged on the wrong ticket.
Rules
- Only Owners and Admins create corrections, in the browser; the operation is not available to API tokens.
- The original must be in a closed period and must not itself be a correction.
- The correction inherits the original's author, ticket, project, billing client, and category. Its date and attribution are fixed and cannot be edited afterwards.
- Minutes are signed and non-zero. The running net of the original plus its corrections, in chronological order, may never go below zero.
- Today's period must be open; if it is already closed, the correction is refused.
- A correction that has been priced by a billing run cannot be deleted.
Example
September is closed. A consultant logged 120 minutes on ACME-184 but did 90. On 3 October an Admin opens the entry and posts a correction of −30 minutes. September's timesheet keeps 120; October's run shows a −30 adjustment line for Nordic Retail.