Qaden — SLA & Agile Health for Jira
SLA management and Agile engineering health, built entirely on Atlassian Forge
Qaden brings priority-based SLA tracking and Agile sprint health metrics to any Jira Cloud project. Configure time-based SLAs with business-hour calendars for customer-facing work, and enable 10 Agile SLA types to measure delivery predictability, sprint hygiene, and team velocity — all inside Jira, with no external infrastructure.
Key Features
Priority-Based SLA Goals
Set different time targets per priority (P1, P2, P3…) within a single SLA definition. Goals cascade top-to-bottom and the first match wins.
Business-Hour Calendars
SLA time counts only during configured working hours. Define schedules per day, public holidays, and IANA timezones. A built-in 24/7 calendar is always available.
Agile Sprint Health
10 Agile SLA types — from point-based aging and spillover to scope creep and sprint predictability — combine into a weighted Sprint Health score per team.
Issue Panel & Context
Live SLA countdown timers, aging risk badges, delivery risk scores, and sprint context appear directly on every Jira issue.
Dashboard Gadget
SLA breach rates, Sprint Health trend lines, projected sprint completion, and ranked team health tables — all in a native Jira dashboard gadget.
Auto-Labeling & Notifications
Breached issues are automatically labeled in Jira. Your project notification scheme handles the rest — no external integrations required.
SLA Management
Time-based commitments for every Jira issue — measured accurately against your team's actual working hours.
Priority-Based Goals
Each SLA definition holds one or more goals ordered by priority tier.
Goals are evaluated top-to-bottom per issue — the first match wins. A catch-all "All remaining" goal ensures no issue is left without a target.
A single SLA named "Time to Resolution" can target P1 issues at 4 hours, P2 at 8 hours, P3 at 24 hours, and everything else at 48 hours.
Business-Hour Calendars
SLA time accumulates only during the hours your team actually works.
Each calendar defines working hours per weekday (with multiple segments supported), an IANA timezone, and a list of public holiday exclusions.
A built-in 24/7 UTC calendar is always available. Custom calendars can be created and assigned per goal — different priorities can use different schedules.
Start, Pause, and Stop Conditions
Every goal has independently configured conditions that control when the SLA clock runs.
- Start — clock begins when the issue enters a specific status (e.g. "Open")
- Pause — clock freezes while the issue sits in a holding status (e.g. "Waiting for Customer")
- Stop — clock halts permanently when the issue reaches a terminal status (e.g. "Done")
Status dropdowns are populated directly from your Jira project, so conditions always match your actual workflow.
Real-Time Breach Detection
A scheduled engine evaluates all running SLA instances every five minutes.
When elapsed business time exceeds the goal target, the instance moves to BREACHED and the issue receives an automatic sla-breached label in Jira.
Issues approaching the target (≥ 80% elapsed) are labeled sla-at-risk in advance, giving teams time to act before a breach occurs.
Issue Panel Display
Every Jira issue shows its active SLA timers in the right-hand panel.
A color-coded progress bar and status badge (On Track / At Risk / Breached / Paused / Met) give an immediate read on SLA state without leaving the issue.
Audit Log
Every configuration change — SLA created, goal updated, calendar modified, access mode changed — is recorded with the acting user and a timestamp.
The audit log is capped at 500 entries and is accessible from the admin panel under the Audit Log tab.
Agile SLA — 10 Engineering Health Metrics
Enable any combination per project. Each type is independently configurable with its own thresholds and evaluated at the right moment in the sprint lifecycle.
Flags issues that have been in-progress too long relative to their story point size. Define P50 / P75 / P95 hour thresholds per story-point band. Amber and red badges appear on the issue panel.
Tracks issues committed to a sprint that were not completed by sprint close. Records spillover count and percentage over time for trend analysis.
A composite risk score combining aging severity, spillover history, and reassignment signals into a single LOW / MEDIUM / HIGH rating per issue.
Compares story points committed at sprint start against points actually delivered at sprint close. MET / AT_RISK / BREACHED thresholds are configurable.
Checks that sprint issues have estimates, assignees, and descriptions before sprint start. Surfaces the percentage of under-prepared issues so problems are caught early.
Uses the coefficient of variation across the last N sprints to score delivery consistency. A lower CV means the team ships predictably sprint over sprint.
Measures story points added to a sprint after it started, expressed as a percentage of the original commitment. Configurable MET / AT_RISK / BREACHED thresholds.
Calculates the standard deviation of commitment accuracy over recent sprints. Lower deviation means more consistent delivery. Requires at least three data points to activate.
The percentage of sprint-committed issues not finished and carried over to the next sprint. Focuses on the count of items, not just points — highlighting broken commitments.
Issues completed in the sprint that were not part of the original sprint commitment. High unplanned work inflates velocity and distorts team planning accuracy.
Sprint Health Score
All enabled Agile SLA dimensions roll up into a single weighted score from 0 to 100. The score gives engineering leaders a single number to track team health sprint over sprint without needing to interpret each metric individually.
Scores are banded into Healthy (≥ 75), At Risk (≥ 50), and Unhealthy (< 50). A 10-sprint trend line in the dashboard gadget shows whether the team is improving or regressing.
Dimension weights are fully configurable per project from the admin panel using sliders that must sum to 100%. The defaults are a balanced starting point and can be adjusted to match what matters most to your team.
Teams
Real engineering teams often split work across multiple Jira projects — a Frontend project, a Backend project, a QA project — all sharing one sprint board. Qaden's Teams feature groups those project keys together so sprint-level SLAs aggregate correctly.
Issue-level SLAs (aging, spillover, delivery risk) remain per-project since rules differ by issue type. Sprint-level SLAs (commitment accuracy, velocity stability, sprint health) aggregate across all projects in the team. Single-project setups work without any team configuration.
Point-based aging, spillover, delivery risk — rules differ by project and issue type. Each project is evaluated independently.
Commitment accuracy, velocity stability, scope creep, carryover rate, sprint health — aggregated across all project keys in the team.
Where Qaden surfaces in Jira
Three distinct surfaces — each optimised for a different audience and workflow.
Issue Panel
- ✓SLA countdown timers per active goal
- ✓On Track / At Risk / Breached / Paused / Met badges
- ✓Aging risk badge for story-point-sized issues
- ✓Delivery risk score and spillover flag
- ✓Sprint context block with health score
Admin Page
- ✓Create and edit SLA definitions with priority goals
- ✓Build and manage business-hour calendars
- ✓Configure 10 Agile SLA types per project
- ✓Manage cross-project Teams
- ✓Full audit log of all configuration changes
Dashboard Gadget
- ✓SLA breach rate donut chart
- ✓Sprint Health ranked table, worst-first
- ✓10-sprint trend lines per team
- ✓Projected sprint completion breakdown
- ✓Issue-level agile stat strip
No external servers. No data leaving Jira.
Qaden runs entirely within the Atlassian Forge runtime. All computation, storage, and scheduling happens inside Jira Cloud using only the permissions granted during installation. There is no middleware, no external database, and no third-party processing.
All SLA state, configuration, and audit records are stored in Forge storage — inside your Atlassian Cloud organisation.
Qaden uses only the scopes granted at install time: read Jira work, write labels, post comments. No admin-level access required.
The five-minute SLA evaluation tick runs as a Forge scheduled trigger. No external cron jobs or polling infrastructure.
Built With
Frontend
- Forge Custom UI
- React
- TypeScript
- @forge/bridge
Backend
- Forge functions
- Forge storage
- Jira REST API
- Agile REST API
Infrastructure
- Atlassian Forge
- Jira Cloud