Skip to main content
Skip table of contents

SLA Time and Report Release notes

This page contains a summary of the latest updates for our app on the Atlassian Marketplace.
Stay up to date with all the latest improvements, features, and technical updates in SLA Time and Report for Jira (Cloud).
We continuously enhance the app to make SLA and OLA management even more powerful, stable, and user-friendly.

Version 5.9.0

Improvements:

  • Minor version update.


Version 5.8.0

Improvements:

  • Minor version update.


Version 5.7.0

Improvements:

  • Minor version update.


Version 5.6.0

Improvements:

  • Optimized SLA notifications engine to improve the speed and stability of pre-breach alerts.

  • Reduced background job load for large-scale projects with multiple SLA configurations.

  • Ensured more consistent delivery of notifications across Jira instances.


Version 5.5.0

Enhancements:

  • Optimized the logic of comment processing in SLA conditions to reduce latency and avoid duplicate triggers.

  • Improved synchronization between SLA timer updates and comment-based triggers.


Version 5.4.0

Enhancements:

  • Optimized SLA recalculation mechanism, making the process faster and more reliable when updating large datasets.

  • Minor interface and usability improvements to support smoother user experience.


Version 5.3.0

Improvements:

  • UI enhancements for SLA configuration and chart visualization.

  • Updated app internals to align with Jira Cloud performance standards.


Version 5.2.0

Fixes:

  • Resolved edge cases where recalculated SLAs were not reflected instantly.

  • Improved data caching for faster report loading.


Version 5.1.0

New feature: Notification before SLA breach
We’ve added a proactive pre-breach notification system that alerts users when an SLA is close to being violated.
You can now:

  • Configure alerts at a specific threshold (e.g., 70%, 80%, or 90% of time consumed).

  • Receive notifications via Jira comments.

  • Take action before deadlines slip and prevent missed SLAs.

This feature helps teams act proactively, not reactively, improving SLA compliance rates and customer satisfaction.


Version 5.0.0

Technical update:

  • Updated required scopes to meet Atlassian Cloud compliance and permission model:
    read:project-role:jira, write:issue.watcher:jira.
    These changes ensure secure access control and proper permission management.


Version 4.2.0

Improvements:

  • Minor UI updates to improve the clarity of SLA configuration fields.

  • Enhanced the rendering speed of SLA Gadgets on Jira Dashboards.


Version 4.1.0

Fixes:

  • Fixed minor bugs.

  • Optimized app load time and SLA refresh rate.


Version 4.0.0

Major update:

  • Updated comment logic used in SLA conditions to increase flexibility in trigger setup.

  • Improved SLA widget visibility logic: now visible only in projects that have SLA rules configured.

  • Adjusted UI scaling for better readability on different screen sizes.

  • Updated required scopes for extended Jira integrations, including screen and project configuration entities.

These changes improve overall compatibility with Jira’s evolving structure and ensure more precise condition handling.


Version 3.5.0

New feature:

  • Added transition support between SLA goals based on the time already worked.
    This allows teams to re-evaluate SLA goals dynamically during issue progress (for example, when switching from “In Progress” to “Waiting for Customer”), providing more accurate SLA tracking.


Version 3.4.0

UI/UX improvements:

  • Migrating the main page to Forge.


Versions 3.3.0 – 3.2.0

Fixes:

  • Resolved several minor bugs and improved internal error handling.

  • Enhanced stability of SLA Grid loading for large Jira instances.


Version 3.1.0

New feature: SLA in Remaining or Elapsed Time
You can now switch between two SLA display modes – Remaining Time and Elapsed Time.
This improvement helps you:

  • Instantly see how much time is left or already spent on each SLA.

  • Identify overdue work faster and take preventive action.

  • Gain better visibility into time-to-resolution and time-to-response performance.

This update enhances real-time SLA visibility for both support agents and managers.


Version 3.0.0

Major technical update:

  • Required scopes changed (due to Forge migration).
    To support the migration to Atlassian Forge and ensure full compatibility with new Jira Cloud APIs, we updated the required scopes.

    <expand title="View list of added scopes"> The following scopes were added:

    • storage:app, read:app-data:jira, write:app-data:jira, read:issue:jira, read:comment:jira, read:comment.property:jira, read:group:jira, read:project:jira, read:user:jira, read:avatar:jira, write:dashboard.property:jira, write:issue:jira, write:comment:jira, write:comment.property:jira, write:issue.property:jira, read:board-scope:jira-software, read:sprint:jira-software, read:app-user-token, read:app-system-token, read:jira-user, read:jira-work, manage:jira-webhook, manage:jira-configuration, read:servicedesk-request


Versions 2.18.0 – 2.17.0

June–July 2025

Improvements:

  • Minor UI improvements to enhance the visual experience.

  • Increased consistency in field alignment and color palette across the app.


Version 2.16.0

Fixes:

  • Fixed bugs in SLA Manager interface and SLA sorting module.

  • Improved calculation accuracy in multi-project reports.


Version 2.15.0

Major improvements:

  • Added SLA sorting by elapsed time to help prioritize overdue work.

  • Redesigned SLA Manager interface for a more modern and intuitive layout.

  • Enhanced overall performance of SLA report rendering.


Version 2.14.0

Improvements:

  • Minor version update.


Version 2.13.0

Fixes:

  • Analytics module improvements and bug fixes related to SLA metrics calculation.


Version 2.12.0

New feature:

  • Introduced custom field support for multi-project SLA tracking.
    You can now use any Jira custom field (e.g., “Team”, “Service”, or “Complexity”) as part of SLA conditions and goal definitions.
    This allows for greater flexibility and tailored SLA logic across multiple projects.


Version 2.11.0

Enhancements:

  • Added SLA gadgets for all chart types, including Met vs Exceeded and Pie Charts.

  • Updated date range logic to be more accurate and consistent across reports.

  • Updated terminology from issue to work item in line with Jira’s new naming convention.


Version 2.10.0

Improvements:

  • Optimized scheduler performance to reduce SLA refresh delays.


Version 2.9.0

Enhancements:

  • Increased limits for SLA notification processing, allowing higher load support for enterprise-level usage.


Version 2.8.0

Improvements:

  • UI adjustments for better user experience.

  • Refactored the Permissions page for clarity and usability.


Versions 2.7.0 – 2.6.0 – 2.5.0

March–April 2025

Fixes:

  • Bug fixes and UI stability improvements across SLA reports and dashboards.

  • Optimized SLA recalculation logic after configuration updates.


Version 2.4.0

UI improvements:

  • Minor design adjustments to align the SLA Manager interface with the new SaaSJet style.


Version 2.3.0

Updates:

  • React refactor for Permissions page and SLA Manager sidebar.

  • Improved rendering performance for complex SLA configurations.


Version 2.2.0

Fixes:

  • Minor Hotjar integration fixes and analytics optimization.


Version 2.1.0

Technical:

  • Migration manifest update for Forge transition.


Version 2.0.0

Major release:

  • The Forge version of the app has been published!
    This migration improves app performance, scalability, and compliance with Atlassian Forge’s enhanced security standards.


Versions 1.4.21–1.4.20

January–February 2025

Technical update:

  • Updated required scopes for Jira Cloud API compliance:
    access_email_addresses, act_as_user, admin, delete, project_admin, read, write.

  • Stability improvements and early Forge readiness setup.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.