Work logs, time, cost and value

  • Work logs. Hours per issue, at the hourly rate in effect when the time was logged. A later rate change never rewrites history.
  • Corrections. The author can correct a work log for 15 minutes. A project lead can correct any, and only a lead can change the rate.
  • Currencies. One currency per project, with an organization default.
  • A first figure. Where an issue has no work log yet, Quasar proposes one from the time the issue spent In progress. Nothing is recorded until someone confirms it.
  • Agent sessions. The time an agent spends is measured by Quasar's clock and proposed as a work log. Since 2026.10.21 an agent can also report the tokens a session used when it closes it.
    • A person confirms it (since 2026.11.1). By default only a person turns a session into a work log; no key can, a lead's included. An organization can let keys confirm, which asks for a fresh second factor.
    • The sessions tray (since 2026.11.1). An icon in the top bar counts the sessions waiting for you, across issues. From it you confirm one or several, set one aside for later, or attach a session that has no issue to the right one.
    • Service accounts' sessions (since 2026.11.1) are confirmed by the lead of the issue's project, or by an organization administrator when they belong to no issue. The work log stays the service account's and records who confirmed it.
  • A person's own session (since 2026.10.21). Supervision time outside the agent's turns: open and close it from the browser; overlaps with other sessions are shown.
  • Internal cost beside the selling rate (since 2026.10.21). Each work log also records what an hour costs, visible to leads only. Actuals are computed on cost, quotes on price.
  • The value report (since 2026.10.21). Price, cost, margin and multiplier per sprint and project, with a ceiling shown when the figures are partial. Agent tokens are priced from the organization's price list.