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 — no rate means their time contributes zero to direct costs, and the overhead coefficient K inflates for everyone else. The system raises overhead warning but still produces skewed reports.
  • Keep MONTHLY rate values realistic — anything above $50,000/month on a zero-activity employee triggers a warning. Typos here go straight into the numerator of K and distort every project's cost.
  • Set correct effective dates on rates — the system uses the latest rate valid in the period. Retroactive edits shift historical K on the next full recalculation (cron on the 1st at 03:00).
  • Deactivate leavers properly — set users.is_active = false. An active MONTHLY employee with no activity lands in admin_salary every month until deactivated.
  • Keep department memberships clean — K is computed per department per month. Stale memberships after a transfer can double-count or land activity in the wrong department.
  • Treat every overhead warning as a signal that K for that department-month is polluted; reports still generate, but numbers are suspect until resolved.

For developers​

Things to do in your daily workflow.

  • Always include the task key in Git branch names — this is the only way activity is mapped to tasks. 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 becomes non-task time and either redistributes onto your other tasks in the period — inflating them — or vanishes from project cost entirely.
  • Install all three plugins — IDE, browser, CLI. Partial installation doesn't just lose activity; it distorts the proportions used when non-task time is redistributed across tasks.

One-sentence summary​

Pair your integrations, configure rates on real dates for everyone, deactivate leavers — and as a developer, always put the task key in the branch name and install all three plugins.