Skip to main content

Data Accuracy Checklist

A quick checklist to keep cost analytics accurate. See the Cost Methodology for the formulas behind each rule.

For admins​

Things to configure and keep clean in the system.

  • Connect both sides of each integration — tracker + Git must be paired: Jira + GitHub/GitLab, Yandex Tracker + GitHub/GitLab, or ClickUp + GitHub/GitLab. Only then can activity be mapped to tasks.
  • Configure a rate for every employee with activity — a day without an active rate is not priced at all. The finance screens list such people under Employees without a rate; their time stays out of every total until a rate covering those days is set.
  • Set correct start and end dates on rates — each day is priced with the rate in force on that day. A rate with the wrong start date leaves days unpriced or prices them at the wrong amount. Overlapping rates are resolved in favour of the most recently created one, so close the old rate when you add a new one.
  • Deactivate leavers properly — a salaried employee who logged no task in a closed month is listed under Employees without tasks, and that month's salary is not attributed anywhere. Deactivate leavers so they stop appearing there.
  • Keep department memberships clean — only active memberships are counted. A stale membership after a transfer can send a task to the wrong department's costs.
  • Treat every warning as a signal — Employees without a rate and Employees without tasks mean money that is missing from the totals. Reports still generate, but the totals are incomplete until the cause is fixed.
  • Read open months as provisional — while a month is open, its amounts can still grow. They become final when the month closes on the 8th of the following month.

For developers​

Things to do in your daily workflow.

  • Always include the task key in Git branch names — the branch is the main way activity is mapped to a task. Commit messages, PR titles, and open Jira tabs are not used.
    • feature/PROJ-123-add-login, bugfix/ABC-45
    • fix-login-bug, sergey/wip, main
    • Work on a branch without a key is counted as activity but is not priced on any task. If a whole day has no task, it also drops out of your day pool, and your other days cost more.
  • Install all three plugins — IDE, browser, CLI. A missing plugin loses task time: a day with real work but no recorded task drops out of the day pool, and the time split between tasks on a day is skewed.

One-sentence summary​

Pair your integrations, set rates with correct dates for everyone, deactivate leavers, and act on every warning — and as a developer, always put the task key in the branch name and install all three plugins.