Measurements & Jira
Enter numbers by hand or pull them from Jira.
Once a cycle is active, it needs numbers. Measurementsare the raw values for each metric and person — for example “18 story points against a target of 20.” You enter them by hand, pull them automatically from Jira, or a mix of sources.
The Measurements hub
Measurementsin the sidebar is your task list: every cycle that needs attention, with how complete its entry is, whether its last Jira sync succeeded, and whether it is waiting to be calculated. Each card’s button takes you straight to the next step — enter values, calculate, or view results.
The measurement grid
Opening a cycle from the hub takes you to its workspace: one row per person and one column per metric. Click a cell to type a value; changes save automatically. A completeness summary shows how many cells and members are filled in, so you know when a cycle is ready to submit.
The same workspace hosts Jira sync, an on-demand refresh for violation- and team-based metrics, and the submit and calculate actions below — everything for running the cycle in one place. You can still reach the same grid from the cycle’s own admin page, which stays the place to activate, lock, or close a cycle and to review approvals, bonuses, and history.
Connecting Jira
KManagement can read data straight from Jira so you do not count it by hand. An Admin or Manager connects Jira once, from Settings → Integrations. You sign in through Atlassian’s own consent screen — the app never sees your Atlassian password.
After connecting, a metric can be mapped to a Jira source: a project or a search query, plus how to aggregate the matching issues. Common examples include the sum of story points, the share of issues delivered on time, the count of overdue issues, and days with missing worklogs.
Syncing values
Mapped metrics are filled in for you. You can refresh them:
- On demand— click “Sync from Jira” in the workspace.
- On a schedule — automatically at set intervals.
Metrics linked to the violation logor to a team’s own cycle (team aggregates, see Team KPIs) have their own “Refresh” button in the workspace, so you can pull in the latest counts without waiting for calculation.
Manual overrides and provenance
You can always type a value over a synced, violation, or team-aggregate one — a manual entry always wins and a later refresh will not replace it. Every value keeps its provenance: a small badge shows where it came from (manual, Jira, a violation record, or a team roll-up), plus who entered it and when. If you overrode a non-manual value, the grid notes that too, for example “synced from Jira at 09:30, overridden by a manager.”
Note
Provenance means the numbers are always traceable. If a score looks off, you can see at a glance whether a value was pulled automatically, computed from another team, or entered by hand — and by whom.
Submitting and calculating
When entry looks complete, submit finalizes it: the cycle moves from Active to Locked and the grid becomes read-only. If some members are still incomplete you get a warning first, so nothing is submitted by accident.
Once locked, Calculateruns the scoring engine: it rolls each person’s measurements up into an achievement percentage, applies the grade scale, and records the result. From there you can open each person’s dashboard to see their score and grade.