Set up a KPI
- Open a Jira dashboard and choose Add gadget. Search for KPI Gauge and add it.
- In the gadget's settings, enter a title and a JQL query. Any query that works in issue search works here.
- Choose what to measure: the number of issues, or the sum of a number field such as Story points.
- Optionally set a target, whether lower or higher is better, and warning and critical limits.
- Optionally add a trend chart (last 14 days, 8 or 12 weeks, or 6 months) by created, resolved or updated date. With a trend, the big number shows the latest period.
- Pick an auto-refresh interval for wallboards and TVs, then save.
Example KPIs
| KPI | JQL |
|---|---|
| Open P1 bugs | type = Bug AND priority = Highest AND statusCategory != Done |
| Issues resolved per week | project = WEB with a 12-week trend by resolved date |
| Story points done | type = Story AND statusCategory = Done, summing Story Points |
| Unassigned support tickets | project = SUP AND assignee is EMPTY AND statusCategory != Done |
| Overdue issues | duedate < now() AND statusCategory != Done |
FAQ
Who sees which numbers? Every number is calculated as the person viewing the dashboard, so people only count issues they're allowed to see. Two viewers can see different values on the same gadget.
How is the trend calculated? The gadget re-runs your query for consecutive rolling windows (for example, each 7 days) on the date field you choose. "Last 7 days vs previous 7 days" compares two full windows.
Is there a limit? Counts have no limit. Sums add up to 5,000 issues per query, so the dashboard stays fast.
What data does the app store? Only the gadget settings, which Jira keeps with the dashboard. See our privacy policy.
Support
Email support@rimulabs.com. We reply within one business day; see our support policy. Feature requests are welcome.