Business-hours timers
Targets count time inside your configured timezone, workdays and daily hours—not raw wall-clock time.
SLA Guard for Jira · Jira Cloud
Resolution deadlines your team can actually act on.
Track one clear resolution SLA per issue, measured against your working hours—with early warnings, breach visibility and no Jira Service Management requirement.
Built for Jira Software Cloud. Tavron is an independent app developer and is not affiliated with Atlassian.
ISSUE · OPS-142AT RISK
Resolution target
02:18:43business time remainingCreatedWarningDeadline
The gap
Jira Software tracks work.
It does not give every team a resolution SLA.
When service commitments live in spreadsheets, saved searches or someone’s memory, the signal arrives late. SLA Guard puts the deadline and its current risk where the work already happens.
From policy to daily signal
Configure once.
See what matters.
A focused flow from rules to action, with business time handled consistently.
- 01
Define the rule
Scope issues using a guided builder, JQL or a saved-filter snapshot. Set default and priority targets.
- 02
Match your calendar
Choose timezone, working days and hours, pause statuses, holidays and replacement working days.
- 03
Act before breach
See Safe, At risk or Breached state on issues and in operational queues; notify assignees and an optional Jira group.
Verified capabilities
Enough control.
Without an SLA programme.
Every capability listed here is implemented in the SLA Guard product codebase.
Ordered, scoped rules
Create multiple rules, validate scope and set precedence. The first matching active rule wins.
Pause, close and reopen handling
Pause the timer in selected statuses, complete it when work is resolved and resume tracking when an issue reopens.
Warnings and breach email
Notify the assignee and, optionally, a Jira group at the warning threshold and actual breach.
Operational views
Use the issue panel, dashboard summary, permission-filtered at-risk queue, historical breach register and CSV export.
Traceable administration
Review pending changes to active rules and consult an in-app audit log and per-issue event timeline.
Who it is for
Teams with one clear resolution commitment.
Software operations
Teams using Jira Software to manage incidents, defects or time-sensitive operational work.
Team leads
People who need an actionable view of approaching and missed deadlines, not another reporting project.
Jira administrators
Admins who want guided setup, scoped access and controlled changes to live rules.
Deliberately focused: SLA Guard tracks one resolution timer per issue. It is not a multi-metric SLA platform or a substitute for a full service-management programme.
Frequently asked
Straight answers.
Does it require Jira Service Management?
No. SLA Guard is designed for Jira Software Cloud and does not require a Jira Service Management licence.
Can we use different targets for different work?
Yes. Rules can use a default target plus priority-specific targets. You can create multiple ordered rules for different issue scopes; the first active match wins.
Does it track existing open issues?
It can, when an administrator explicitly starts the opt-in backfill. Those timers begin from the present; the app does not invent historical SLA time.
Who can see reports?
Jira administrators have access by default. Viewer and CSV-exporter groups can be configured separately, while Jira issue permissions continue to apply.
What happens when an active rule changes?
The edit becomes a pending version. An administrator reviews and promotes it before it affects new matching work; existing timers retain their captured target and schedule.
Is Tavron an Atlassian partner?
This site does not claim an Atlassian partnership. Jira and Atlassian are trademarks of Atlassian and are used only to describe compatibility.
Marketplace
Preparing for public availability.
The Marketplace listing and installation link are not public yet. Contact us to ask about availability.