Atlassian · Jira Service Management Cloud
SLA & Time to Resolution Reports
First-response and resolution reports against Jira Service Management SLA targets.
- Works with Jira Service Management Cloud
- Marketplace Atlassian Marketplace
Coming soon
Coming to the Atlassian Marketplace
Public documentation is available. Public installation and purchase are unavailable. Marketplace submission and approval have not been verified; live JSM and production licence acceptance remain open.
Coming soon toAtlassian Marketplace
What it does
Review native Jira Service Management SLA cycles, first-response and resolution outcomes, completed-cycle breach trends, and priority and issue-type breakdowns. Choose a service project and request-created dates, select its exact SLA metrics, then export CSV detail or a PDF summary. Jira Service Management remains the source of truth for goals, pauses, calendars and breach outcomes.
Capabilities
Native SLA outcomes
Select exact first-response and resolution SLA metrics, including custom or translated names. Completed-cycle compliance counts known met and breached outcomes; ongoing cycles and unknown outcomes remain separate.
Breach trends and breakdowns
Review completed cycles by their stop month in UTC, plus current request priority and issue type. Reopened requests may contribute multiple cycles.
CSV and PDF exports
Your browser generates CSV detail and a PDF summary with cohort, selected metrics and coverage information. Downloaded files contain request keys and metrics.
Independent working-hours preview
Compare elapsed time for a chosen UTC interval using an IANA time zone, weekday working hours and holiday dates. This preview does not change native Jira SLA values. Settings reset on reload.
Visible coverage limits
Select up to 93 days and scan at most 500 requests. Missing SLAs, inaccessible requests and truncated SLA pagination are coverage gaps to review before using the figures.
Read-only reporting
The Forge app reads as the signed-in user with read:jira-work. It has no app report or configuration storage and no app-configured external reporting destination.
Questions
Where does SLA & Time to Resolution Reports run?
The application runs on Atlassian Forge. Atlassian hosts its code and processes its requests. Atesen Software does not operate an external app server or report database. This is a hosting description, not a certification or trust-badge claim.
What does SLA & Time to Resolution Reports connect to?
App reporting calls go to Jira through Forge asUser. The manifest configures one read-only scope, read:jira-work, with no external egress or remotes. There is no third-party reporting service or app analytics integration. Atlassian platform processing is governed separately.
How do I get help with SLA & Time to Resolution Reports?
Support for SLA & Time to Resolution Reports is provided by email in English and Turkish. Public installation and purchase are not yet available.
Email support@atesensoftware.com. We aim to acknowledge every support email within two business days (Europe/Istanbul).
What we do not claim
- Public docs do not establish Marketplace approval, public installation, customers or sales. Authenticated native-SLA scenarios and active, trial and inactive production licence behavior remain unverified.
- Reports require Jira Service Management requests with configured native SLA metrics and access to read them. General Jira software and business projects are not supported for these SLA reports.
- A report covers requests created in the selected period, not every cycle completed in that period. All returned cycles for that request cohort are included.
- The app does not create SLA rules, edit Jira calendars, send alerts, schedule reports or provide a general time-in-status or workflow audit.
- No security certification, third-party audit or Atlassian trust badge is claimed.
Marketplace
Atlassian Marketplace: Coming soon. No verified public listing, installation link or checkout.
Coming soon toAtlassian Marketplace