AutoChase documentation

Getting started

Install AutoChase, connect your Jira projects, define SLAs, configure organisation structure, and set up capacity planning.

1. Install AutoChase from the Atlassian Marketplace.
2. Open Jira → Apps → AutoChase (or Manage apps → AutoChase).
3. Add Projects from Jira and assign default SLAs and teams.
4. Create SLA rules with response/resolution times, reminders, leadership visibility, and working hours.
5. Open Organisation and add at least one department, team, and escalation hierarchy record.
6. Open Capacity planning → Setup (gear icon). Configure estimate source, default hours, and story points if needed → Save settings.
7. Use Capacity planning → Availability for leave, recurring meetings, and per-person overrides.
8. Review Sprint commitment and Backlog pressure to see workload vs capacity.

Navigation in the app: Dashboard · Tracked issues · Reports · Capacity planning · Projects · SLA rules · Organisation

Dashboard

High-level SLA health and capacity snapshot across tracked projects.

KPI cards

When capacity data is available, additional KPIs show team utilization and overload counts.

Project filter

Use the global project filter at the top to narrow dashboard metrics to selected projects.

Issues at risk of breach

At-risk and breached open issues, sorted by urgency. Columns include Issue, Project, Organisation, Assignee, SLA, SLA progress, and Reminders & escalation.

Top breached projects

Up to five projects with the most breaches in the current filter scope. Use View to jump to Tracked issues filtered by that project.

Tracked issues

Live SLA monitoring with reminders, escalation, and per-issue controls.

Filters

• Status: All, On track, At risk, Breached, Resolved
• SLA tracking: All SLA, SLA on, SLA off
• Project filter — limit to selected AutoChase projects
• Search — issue key, summary, project, assignee, department, team

Table

Sync issues (Projects tab) assigns the project default SLA only. Use Track to pause enforcement without removing the issue from the list.

Reports

Shareable SLA summaries for teams and leadership. All report types include SLA metrics. Capacity is optional for Leadership and Full reports only.

Report types

Options

• Team — limit to one team or all teams
• From / To — optional date range for SLA tickets (leave empty for full history)
• Output — Preview on screen, Export CSV, or Save as PDF (via print dialog)
• Include capacity — checkbox for Leadership digest and Full report only; adds a capacity snapshot at generation time

Click Generate to build the report. Preview appears below; CSV downloads; PDF opens the browser print dialog.

Capacity planning

See open Jira work against each person’s capacity. AutoChase combines SLA deadlines with workload so you can spot overload before breach.

Capacity planning uses six sections (sub-tabs):

Sprint commitment

Plan a specific Jira sprint: compare demand (assigned work in the sprint) to supply (available hours after meetings, leave, and focus factor).

Summary KPIs: Demand (h), Supply (h), Utilization %, Gap (h), Overloaded count.

Positive gap means more work is assigned than the team can deliver in the sprint window. Sprint commitment is board-scoped — pick the board that matches how your team plans sprints.

Backlog pressure

Open workload vs weekly capacity (not sprint-length). Use this for ongoing backlog health.

Filters: projects, group by (person or project), time window (All open, Sprint, Outside active sprint, Updated this month/year), utilization band, and search. Per overloaded person, use Set Xh/wk to apply a recommended weekly hours override.

Capacity Reports (sub-tab)

On-demand exports for planning meetings — distinct from the main Reports tab (SLA-focused).

Generate on screen, then Export CSV or Export Excel (.xlsx with formatted matrix).

Velocity

Throughput trends from closed sprints on a Jira board. Use for forecasting and comparing team members.

• Board — velocity is read from closed sprints on this board
• Sprints — recent closed (last 3/6/9/12) or pick specific closed sprints
• Chart — hours or story points
• Compare people — optional overlay lines on the trend chart

Click Apply after changing filters. Charts show team throughput; tables show per-person velocity summary and sprint-by-sprint breakdown. An upcoming sprint forecast uses historical velocity when board data is available.

Availability

• Leave — personal leave periods reduce sprint supply
• Recurring meetings — templates and per-person meeting blocks
• Person overrides — custom weekly capacity or meeting hours for one person
• Focus factor — team-wide share of capacity for focused sprint work (configured in Setup)

Setup (gear icon)

One-time team defaults for capacity math. Change rarely — use Availability for day-to-day leave and meetings.

Click Save settings after changes, then Refresh on the relevant capacity tab.

How demand is calculated

1. Uses Remaining estimate (or Original estimate / Story points per your setting)
2. Per-project overrides apply when configured
3. If time estimate is missing, uses minutes if missing or story points × hours/point
4. Unassigned issues can appear in a separate unassigned pool

Capacity on the issue panel

When capacity planning is enabled, the issue side panel shows assignee workload vs SLA resolution time remaining — capacity at risk when backlog exceeds time left before breach.

Projects

Choose which Jira projects AutoChase tracks. Projects define SLA scope and capacity scope.

Sync and add

• Sync projects — pull project metadata from Jira
• Sync issues — pull issues into AutoChase tracking
• Load projects — populate dropdown from Jira
• Owner email (required) — used for escalation when tickets are unassigned

Per-project configuration

• Issue types to track — limit which types are imported
• Default SLA — applied on sync for new issues
• Team — links project to organisation structure for reports and escalation

Project actions

Edit, Assign SLA, Assign team, or Remove.

Use Capacity planning for workload and sprint planning; use Reports for shareable SLA summaries.

SLA rules

Define response and resolution targets, reminders, leadership visibility, SLA clock behavior, and working hours.

SLA modes

• Single SLA — same response/resolution for all priorities
• Priority-based SLA (P1–P5) — different targets per priority

Five-step wizard

1. SLA Timing — name, times, warning threshold, scope, SLA clock, working hours
2. Acknowledgment reminders — up to 3 percentages of response time
3. Progress reminders — up to 3 percentages of resolution time
4. Leadership visibility levels — manager-chain thresholds
5. Review & submit

Key fields

Status lifecycle

On track → At risk (warning %) → Breach (resolution exceeded)

Working calendar

Configure when SLA time counts — business hours, weekends, short days, holidays, and timezone.

Configure working time in SLA rules → Create/Edit SLA → Step 1 → Working time.

Enable business hours

Check Count this SLA only during working hours. When enabled, SLA budgets (e.g. 16 hours) advance only during configured windows. Nights, unchecked days, and holidays do not count.

Timezone

Searchable IANA timezone picker. Use Use my timezone for a quick start. All day/time rules apply in this timezone.

Work days and hours

Same hours every day

• Check Mon–Fri (default); uncheck Sat and Sun to exclude weekends
• Set Start (e.g. 09:00) and End (e.g. 17:00)

Different hours per day

Enable Set different hours for each day. Example: Mon–Thu 09:00–17:00, Friday 09:00–13:00 (half day).

Holidays

• Enter dates as YYYY-MM-DD (one per line)
• Upload CSV, TSV, or Excel (.xlsx)
• Use presets: US federal, UK bank, India public, EU common, APAC mix (2026)
• Download template for bulk import

Organisation

Departments, teams, and escalation hierarchy in one place.

Departments

Organizational buckets for analytics and escalation context. Add name and optional description. Create departments before teams.

Teams

Group people and projects under a department. Assign teams to projects from the Projects tab. Used by Reports team filter and org columns on issues.

Escalation hierarchy

Upload org structure for manager-chain leadership visibility.

1. Download template (columns: employee_id, name, email, reports_to_id)
2. Import CSV, TSV, or Excel (.xlsx)
3. Click Resolve Jira IDs to link emails to Jira accounts
4. Verify in the table; use Add employee for manual edits

Leadership visibility levels in SLA rules walk the manager chain from the assignee using this hierarchy.

How it works

End-to-end flow once projects, SLAs, organisation, and capacity are configured.

1. Tracking — New issues in enabled projects are tracked (via webhook and sync)
2. SLA assignment — From project default and SLA matching rules; manual override per issue
3. SLA clock — Runs during working hours if configured; pauses on selected statuses
4. Status — on_track → at_risk → breach
5. Reminders — Acknowledgment and progress comments at configured thresholds
6. Leadership visibility — Escalation levels via hierarchy on scheduled checks
7. Capacity — Workload from open issues; compared to weekly hours, sprint supply, and SLA time remaining
8. Resolution — Tracking stops when issue reaches done/resolved

Issue panel

Per-issue SLA and capacity context inside Jira.

Open a tracked issue and select the SLA Status panel.

SLA snapshot

• Status (On track / At risk / Breach)
• Escalation level, Acknowledgment state
• Applied SLA policy and source (auto match vs manual)
• Response and resolution time remaining
• Live SLA progress with business-hours awareness

Capacity snapshot

Assignee workload, weekly capacity, utilization, and whether workload exceeds SLA resolution time left.

Actions

Quick acknowledge and Assign SLA from the panel.

Troubleshooting

Support

For questions or issues, visit our support portal or email support@opusleaf.com.

AutoChase runs on Atlassian Forge. Data stays in your Jira site.