TimeBound documentation
TimeBound adds SLAs to Jira: goals per priority, business-hours calendars, and compliance reports. It is made by Selana Technologies LLC. Support: hello@selana.io, first response within 1 business day.
Where to find it
- Report page: Apps menu, then TimeBound SLA. Also in each project's sidebar (the report starts with that project).
- Issue panel: open any issue and look for SLA in the right-hand sidebar.
- Settings (Jira admins): in the Apps menu, hover TimeBound SLA, click ... and choose App settings. Times in TimeBound are working hours, for example 72h is 9 working days on a 09:00 to 17:00 calendar.
Set up SLAs (Jira admins)
TimeBound starts with two example SLAs on a Monday to Friday, 09:00 to 17:00 UTC calendar: Time to resolution and Time to start work. Change them or add your own. Each SLA has:
- Name.
- Applies to: optional JQL, for example
project = SUP AND issuetype = Bug. Leave blank to apply to every issue in a report. - Calendar: which working hours count. Choose 24/7 to count all time.
- Starts: when the issue is created, or when it enters a status (or any status in a category such as In Progress).
- Pauses while in: optional statuses where the clock stops, for example Waiting for customer.
- Stops when it enters: statuses or categories, for example any Done status.
- Goals: working hours per priority. Leave a priority blank for no SLA. "Any other priority" covers the rest.
Calendars
- Time zone: a name like America/New_York or Europe/London. Daylight saving is handled.
- Working hours per day: like
09:00-17:00, or split shifts like09:00-12:00, 13:00-18:00. Leave a day blank for a day off. - Holidays: dates like 2026-12-25, one per line.
Run a report
- Enter a JQL query, or keep the default (issues created in the last 30 days, or 90 days on a project page).
- Click Run report, then pick an SLA.
You get:
- Tiles: compliance (met divided by met plus breached), breached, at risk (open with 80% or more of the goal used), and open.
- Compliance: a table per priority with goal, met, breached, open, compliance and median time, plus a weekly met and breached chart.
- Breached: every breached issue with the time it breached.
- Open and at risk: open issues sorted by time left, with the due time.
- Copy to spreadsheet: one row per issue per SLA. Paste into Excel or Google Sheets. The Breached and Open lists and this tab also have an Export these issues to Excel with SheetOut link, which opens SheetOut with the report's JQL filled in (SheetOut is a separate app; the link to its listing is next to it).
TimeBound reads issues 100 at a time and shows progress (for example "Read 2,300 of about 5,100 issues"). Click Stop and show what was read to see results for the issues read so far. Reports cover up to 20,000 issues. If your query matches more, TimeBound tells you and reports on the first 20,000; narrow the JQL by project or date. The compliance numbers and the weekly chart cover every issue read; the Breached and Open lists and the spreadsheet tab show at most 5,000 rows each.
Dashboard gadget
Add SLA compliance (TimeBound) to any Jira dashboard: Edit the dashboard, Add gadget, search for TimeBound. In the gadget settings choose:
- SLA: which SLA to show.
- JQL: the issues to measure (default: created in the last 30 days).
The gadget shows compliance, the number breached and at risk, and the 10 running issues closest to breaching with the time left. It reads up to 1,000 issues and says so when your query matches more. Open full report opens the TimeBound report page with the same JQL and runs it.
How SLA time is calculated
- The clock starts at the start condition and stops the first time the issue enters a stop status after that.
- Only working hours in the SLA's calendar count, and time in pause statuses does not count.
- The goal is the one for the issue's current priority.
- Open issues already past their goal count as breached.
- Each issue has one SLA cycle. If an issue is reopened, the first cycle is what counts.
- Everything is calculated from the issue's history when you look, so results never go stale and older issues count too.
Permissions and privacy
TimeBound reads Jira as the signed-in user, so people only see issues they already have access to. It stores only the SLA and calendar settings admins create, never issue data, and sends nothing outside Atlassian. See the privacy policy.
Troubleshooting
| You see | Do this |
|---|---|
| No SLA applies to this issue | Give the issue's priority a goal, or check the SLA's Applies to JQL. |
| SLA scope JQL has a problem | Fix the JQL in TimeBound settings; test it in Jira's issue search first. |
| Reached the 20,000 issue limit | Narrow the JQL by project, issue type or date. |
| Stopped early | You clicked Stop. Run the report again to read every issue. |
| Needs an active subscription | A Jira admin can start a trial or subscription in Manage apps. |
Pricing
Free for up to 10 users. See the Marketplace listing for current prices.