• The "Time to SLA Date" custom field was not using the default Jira CSV date format in CSV exports.
• HTML tags in the issue summary were breaking the SLA Report.
• Calendar was considering half-day holiday working duration on non-business days.
• Removed the 255 character limit on JQL inputs in the Settings page.
• The "Time to SLA" top menu item would break the login page in some cases.
• The "SLA History" tab panel was breaking other panels in some cases.
• Deleting the expired mute SLA option was not working in some cases.
• JCMA migration was not working
• 10.13.3 version was failing to initialize in some DB types.

• The "Time to SLA Date" custom field was not using the default Jira CSV date format in CSV exports.
• HTML tags in the issue summary were breaking the SLA Report.
• Calendar was considering half-day holiday working duration on non-business days.
• Removed the 255 character limit on JQL inputs in the Settings page.
• The "Time to SLA" top menu item would break the login page in some cases.
• The "SLA History" tab panel was breaking other panels in some cases.
• Deleting the expired mute SLA option was not working in some cases.
• JCMA migration was not working
• 10.13.3 version was failing to initialize in some DB types.

Improvements:

• Ability to stop recurring notifications after a specific duration or elapsed percentage has passed.
• Ability to customize SLA columns in the SLA Report.

Bug Fixes:

• SLA History was displaying breach and critical zone events in incorrect locations.
• The working duration was displayed as 0 for ‘No Target’ goals.
• CSV export with Time to SLA Date Custom Fields was occasionally failing.
• Problem related to AO_C5D949_EVENT_INDEX table’s primary key increase problem has been fixed.
• Enabling the ‘Mute SLA’ feature occasionally caused sending notifiers to fail.
• In some cases, slaRemainingDuration custom field sorting was causing problems.

Improvements:

• Ability to stop recurring notifications after a specific duration or elapsed percentage has passed.
• Ability to customize SLA columns in the SLA Report.

Bug Fixes:

• SLA History was displaying breach and critical zone events in incorrect locations.
• The working duration was displayed as 0 for ‘No Target’ goals.
• CSV export with Time to SLA Date Custom Fields was occasionally failing.
• Problem related to AO_C5D949_EVENT_INDEX table’s primary key increase problem has been fixed.
• Enabling the ‘Mute SLA’ feature occasionally caused sending notifiers to fail.
• In some cases, slaRemainingDuration custom field sorting was causing problems.

• Bug fixes
  • Users were able to define SLAs without goal.
  • Exporting SLA configurations were failing when there is a # symbol in the SLA name.
  • Resetting SLAs via REST API was not working in some cases.
  • SLAs with ‘Next Business Days’ goal type were not calculating elapsed percentage correctly.
  • In some instances, some events were excluded from SLA calculations.
  • In some instances, the recalculation page was displaying an error.

• Bug fixes
  • Users were able to define SLAs without goal.
  • Exporting SLA configurations were failing when there is a # symbol in the SLA name.
  • Resetting SLAs via REST API was not working in some cases.
  • SLAs with ‘Next Business Days’ goal type were not calculating elapsed percentage correctly.
  • In some instances, some events were excluded from SLA calculations.
  • In some instances, the recalculation page was displaying an error.

With this version, the Time to SLA JQL 2.0 functions have been removed. You can use this documentation to learn more about JQL 3.0 functions and this documentation to find out which functions to replace the old ones with.

New Feature

• Brand-new Permissions page design.

Bug Fix

• The SLA History panel elapsed percentage display was wrong.
• Cascading Select List custom fields was breaking the SLA Panel and recalculation.
• JSM SLA import was not correctly converting goal durations in some cases.
• The Overdue calculation was incorrect for SLAs with more than one cycle.

With this version, the Time to SLA JQL 2.0 functions have been removed. You can use this documentation to learn more about JQL 3.0 functions and this documentation to find out which functions to replace the old ones with.

New Feature

• Brand-new Permissions page design.

Bug Fix

• The SLA History panel elapsed percentage display was wrong.
• Cascading Select List custom fields was breaking the SLA Panel and recalculation.
• JSM SLA import was not correctly converting goal durations in some cases.
• The Overdue calculation was incorrect for SLAs with more than one cycle.

• Customers using Oracle DB had problems sending notifications.
• Calendar import didn't work in some cases.

• Customers using Oracle DB had problems sending notifications.
• Calendar import didn't work in some cases.

• New Features
  • Ability to mute SLA notifications for a single issue or issues within a JQL filter has been added. More information
• Improvements
  • Ability to create a new report configuration from an existing one is added.
• Bug Fixes
  • slaTargetDate function was not working properly for breached and paused SLAs.
  • Time to SLA custom field’s value was not displayed correctly in the issue navigator detail view.
  • SQL errors were encountered when users utilized Time to SLA’s JQL 2.0 functions in filter subscriptions.
  • Time to SLA automation integration was not triggering the automation audit log.
  • Notification triggering was problematic in some instances.

• New Features
  • Ability to mute SLA notifications for a single issue or issues within a JQL filter has been added. More information
• Improvements
  • Ability to create a new report configuration from an existing one is added.
• Bug Fixes
  • slaTargetDate function was not working properly for breached and paused SLAs.
  • Time to SLA custom field’s value was not displayed correctly in the issue navigator detail view.
  • SQL errors were encountered when users utilized Time to SLA’s JQL 2.0 functions in filter subscriptions.
  • Time to SLA automation integration was not triggering the automation audit log.
  • Notification triggering was problematic in some instances.

• Calendar fetch errors have been eliminated.
• 'No Target' goal type problem, which was causing failures in unexpected places, has been fixed.

• Calendar fetch errors have been eliminated.
• 'No Target' goal type problem, which was causing failures in unexpected places, has been fixed.

• Time to SLA app pages were not loading in some instances due to issues with Tomcat/nginx configurations.
• Critical Zone color change was inconsistent in the SLA Panel and Time to SLA custom field in some cases.
• Working duration analysis gadget was not calculating SLA duration for running SLAs in some cases.
• SLA notifications were being sent for disabled SLAs.
• SLAs with more than one pause event type were miscalculating durations in some cases.

• Time to SLA app pages were not loading in some instances due to issues with Tomcat/nginx configurations.
• Critical Zone color change was inconsistent in the SLA Panel and Time to SLA custom field in some cases.
• Working duration analysis gadget was not calculating SLA duration for running SLAs in some cases.
• SLA notifications were being sent for disabled SLAs.
• SLAs with more than one pause event type were miscalculating durations in some cases.

• Time to SLA is now compatible with Jira 9.

• Time to SLA custom field was not showing the correct duration for users with a language selection other than English.
• TTS was giving numerous error logs if no SLA was present in the Service Management view.

• Time to SLA is now compatible with Jira 9.
• Time to SLA custom field was not showing the correct duration for users with a language selection other than English.
• TTS was giving numerous error logs if no SLA was present in the Service Management view.

• New Features
  • Ability to exclude finished SLAs from regeneration tasks has been added
  • Additional SLA Date JQL functions such as startOfYear and endOfMonth have been added

• Improvements
  • Ability to exclude disabled SLAs from SLA reports has been added
  • New duration formats have been added to SLA reports
  • Ability to exclude SLAs with zero working durations from SLA Working Duration Analysis Gadget has been added

• Bug Fixes
  • SLA Report Saved Configurations search and sorting features were not working correctly
  • Issue search redirects from TTS gadgets were not working as expected in some cases
  • SLA Notifier Log Cleaning task was not working in some instances
  • SLA conditions were not displaying values from contexts other than the default context of select fields
  • SLA Dates custom field was not in line with Jira’s date format when exported to a CSV
  • SLA Duration gadget was not accounting for the business hour set within the calendar

and more...

• New Features
  • Ability to exclude finished SLAs from regeneration tasks has been added
  • Additional SLA Date JQL functions such as startOfYear and endOfMonth have been added

• Improvements
  • Ability to exclude disabled SLAs from SLA reports has been added
  • New duration formats have been added to SLA reports
  • Ability to exclude SLAs with zero working durations from SLA Working Duration Analysis Gadget has been added

• Bug Fixes
  • SLA Report Saved Configurations search and sorting features were not working correctly
  • Issue search redirects from TTS gadgets were not working as expected in some cases
  • SLA Notifier Log Cleaning task was not working in some instances
  • SLA conditions were not displaying values from contexts other than the default context of select fields
  • SLA Dates custom field was not in line with Jira’s date format when exported to a CSV
  • SLA Duration gadget was not accounting for the business hour set within the calendar

and more...

• JCMA integration was not working correctly.
• Business Hours have been added to the eazyBI custom field.

• JCMA integration was not working correctly.
• Business Hours have been added to the eazyBI custom field.

• New Feature:
  • SLA History tab panel can be exported to Excel/PDF.
• Improvement:
  • TTS Date Custom Field searcher has been added.
  • Some messages in French and German were incorrect.
• Bug Fixes:
  • SLA recalculation was not working in some instances.
  • Third party JQL functions were not successfully executed within Asynchronous Calculation scope.
  • Wrongly migrated Reset events were causing calculation problems.
  • Notifier Scheduled Task was not successfully executed in some cases.
  • SLAs entering the pause condition before the start condition was causing incorrect SLA Targets.
  • inCriticalZone JQL function was not working for SLAs with Next Business Day goal type.
  • Disabled SLAs were not removed from TTS Date Custom Field value.

• New Feature:
  • SLA History tab panel can be exported to Excel/PDF.
• Improvement:
  • TTS Date Custom Field searcher has been added.
  • Some messages in French and German were incorrect.
• Bug Fixes:
  • SLA recalculation was not working in some instances.
  • Third party JQL functions were not successfully executed within Asynchronous Calculation scope.
  • Wrongly migrated Reset events were causing calculation problems.
  • Notifier Scheduled Task was not successfully executed in some cases.
  • SLAs entering the pause condition before the start condition was causing incorrect SLA Targets.
  • inCriticalZone JQL function was not working for SLAs with Next Business Day goal type.
  • Disabled SLAs were not removed from TTS Date Custom Field value.

Bug Fix:

• Some migration scope was missing causing no migration to be found.

Bug Fix:

• Some migration scope was missing causing no migration to be found.

New features:

• Added JCMA support. Migrating to the Cloud is now easier than ever. Simply include the Time to SLA in your migration.

Bug fixes:

• The Escalation Service was not running properly in some cases.
• ‘Elapsed Percentage’ showing error when SLA end date was before SLA start date.
• All SLAs inclusion was causing issues with CMJ integration.
• ‘Is Over’ notification trigger was not working properly.
• SLA Dates custom fields were showing dates of SLAs that not started.
• SLAs with negotiation date notifiers were problematic in some instances.
• Notifiers of the migrated SLAs continued to be sent even if the notification was deleted or disabled.
• In some cases, using JQLs of third-party apps was problematic.
• While indexing Jira, there were errors in the logs during the issue cloning, JQL search or issue browsing.

New features:

• Added JCMA support. Migrating to the Cloud is now easier than ever. Simply include the Time to SLA in your migration.

Bug fixes:

• The Escalation Service was not running properly in some cases.
• ‘Elapsed Percentage’ showing error when SLA end date was before SLA start date.
• All SLAs inclusion was causing issues with CMJ integration.
• ‘Is Over’ notification trigger was not working properly.
• SLA Dates custom fields were showing dates of SLAs that not started.
• SLAs with negotiation date notifiers were problematic in some instances.
• Notifiers of the migrated SLAs continued to be sent even if the notification was deleted or disabled.
• In some cases, using JQLs of third-party apps was problematic.
• While indexing Jira, there were errors in the logs during the issue cloning, JQL search or issue browsing.

Integration with Configuration Manager for Jira: Now you can export/import TTS custom fields, SLAs, settings, gadgets, report configurations etc. via CMJ!

Integration with Configuration Manager for Jira: Now you can export/import TTS custom fields, SLAs, settings, gadgets, report configurations etc. via CMJ!

Notice: Starting from this version Legacy SLAs will be migrated automatically. Update your Time to SLA and let it takes you to the next level!

New feature:

• SLA regeneration has been re-designed, you can now:
  • Run regeneration in the background, navigate through Jira and see the progress when you come back.
  • Select SLAs for the regeneration.
  • Cancel the regeneration.

Improvements

• Improved cache mechanism.
• Calendar date formats are now aligned with Jira Look and Feel.

Bug Fixes:

• slaJoin JQL function was not working accurately with date, duration and percentage functions.
• ‘Where is my SLA’ was showing an error when SLA selection was done via keyboard.
• SLA Durations dashboard gadget was preventing the ‘Login & Approve’ dialogue when added to a Confluence page.
• If Next-Gen SLA was using comments as start/end conditions, and the issue had no comments, it was causing NullPointerException stack traces in the log file.
• Postponed Event Checker service was not checking appropriate events.

Improvement:

• Improved cache mechanism.
• Calendar date formats are now aligned with Jira Look and Feel.

Bug fix:

• Postponed Event Checker service was not checking appropriate events

• SLA Migration was finishing before all SLAs are migrated in some instances

• Postponed Event Checker Scheduled Task was causing slowdowns in some instances.

Notice: Starting from this version Legacy SLAs will be migrated automatically. Update your Time to SLA and let it takes you to the next level!

New feature

• SLA regeneration has been re-designed, you can now:
  • Run regeneration in the background, navigate through Jira and see the progress when you come back.
  • Select SLAs for the regeneration.
  • Cancel the regeneration.

Bug Fixes

• slaJoin JQL function was not working accurately with date, duration and percentage functions.
• ‘Where is my SLA’ was showing an error when SLA selection was done via keyboard.
• SLA Durations dashboard gadget was preventing the 'Login & Approve' dialogue when added to a Confluence page.
• If Next-Gen SLA was using comments as start/end conditions, and the issue had no comments, it was causing NullPointerException stack traces in the log file.

• The Migration Tool was not working in some instances.
• Importing SLAs with the default goal was not working.

• The Migration Tool was not working in some instances.
• Importing SLAs with the default goal was not working.

Improvements

• SLA Notifiers can now be configured to have percentages greater than 100%.
• Jira Users, Voters and Watchers can now be used in SLA Notifiers.

Bug Fixes

• SLA goal change was not reflected in issues.
• Sorting with slaRemainingDurationSorter was not working in some cases.
• JSM SLA Import page was showing errors in some cases.
• slaOverdue parameter in SLA Notifiers was not taking the calendar into account.
• Next Business Day was calculating the Target Date wrong if there were multiple intervals in a single working day.
• SLA History Tab Panel was causing javascript errors in some cases.

Improvements

• SLA Notifiers can now be configured to have percentages greater than 100%.
• Jira Users, Voters and Watchers can now be used in SLA Notifiers.

Bug Fixes

• SLA goal change was not reflected in issues.
• Sorting with slaRemainingDurationSorter was not working in some cases.
• JSM SLA Import page was showing errors in some cases.
• slaOverdue parameter in SLA Notifiers was not taking the calendar into account.
• Next Business Day was calculating the Target Date wrong if there were multiple intervals in a single working day.
• SLA History Tab Panel was causing javascript errors in some cases.

New Features

New Features

Improvements

• You can now search issues for particular SLAs.
• Warning dialog shows up if there are unsaved changes on the SLA configuration page.

Bug fixes

• Some JSM specific features were not functioning accurately if the Time to SLA app was installed/enabled before the JSM installation.
• Some TTS admin pages were not adhering to permissions.
• Migrating legacy SLAs with reset was causing migration to fail if the field’s name was changed after it had been selected in the SLA configuration.
• Ascending sorting of the ID column of the SLA configuration table was missing.
• SLA selection in the SLA History tab panel was not working properly.
• Some SLA functions were not working properly for SLAs with multiple goals.
• SLA Report was not displaying selected custom fields.

Improvements

• You can now search issues for particular SLAs.
• Warning dialog shows up if there are unsaved changes on the SLA configuration page.

Bug fixes

• Some JSM specific features were not functioning accurately if the Time to SLA app was installed/enabled before the JSM installation.
• Some TTS admin pages were not adhering to permissions.
• Migrating legacy SLAs with reset was causing migration to fail if the field’s name was changed after it had been selected in the SLA configuration.
• Ascending sorting of the ID column of the SLA configuration table was missing.
• SLA selection in the SLA History tab panel was not working properly.
• Some SLA functions were not working properly for SLAs with multiple goals.
• SLA Report was not displaying selected custom fields.

• New Features
  • isInBusinessHours JQL has been added so users can search for issues that are currently in the business hours.
• Improvements
  • SLA Report page UI has been redesigned.
• Bug Fixes
  • SLA Panel ordering was giving errors in some cases.
  • TTS Date custom field was giving an error if there wasn’t any applicable goal in the issue.
  • Usage of system date fields were sending incorrect errors to logs.
  • Diagnostics report generation was problematic in some cases.
  • Disabling only the default SLA goal and then saving the SLA did not save the SLA correctly.
  • SLA History Tab panel was causing the colors that are selected in Look & Feel to disappear.
  • Escalation Service was not accepting JQLs with more than 255 characters.

• New Features
  • isInBusinessHours JQL has been added so users can search for issues that are currently in the business hours.
• Improvements
  • SLA Report page UI has been redesigned.
• Bug Fixes
  • SLA Panel ordering was giving errors in some cases.
  • TTS Date custom field was giving an error if there wasn’t any applicable goal in the issue.
  • Usage of system date fields were sending incorrect errors to logs.
  • Diagnostics report generation was problematic in some cases.
  • Disabling only the default SLA goal and then saving the SLA did not save the SLA correctly.
  • SLA History Tab panel was causing the colors that are selected in Look & Feel to disappear.
  • Escalation Service was not accepting JQLs with more than 255 characters.

• Display SLA's of linked issue feature was not working if there are only Next-Gen SLAs in the linked issue.
• Only disabling/enabling 'All remaining issues' SLA goal was not resulting in correct save of the SLA
• Calculating overdue duration was causing problems in some cases

• Display SLA's of linked issue feature was not working if there are only Next-Gen SLAs in the linked issue.
• Only disabling/enabling 'All remaining issues' SLA goal was not resulting in correct save of the SLA
• Calculating overdue duration was causing problems in some cases

New Features

• Migration Tool: Ability to migrate Legacy SLA configurations to Next-Gen SLAs
• Ability to define SLA notifier when SLA ends

Improvements

• Project, Issue Type, Components, Affected/Fixed versions, labels can now be used as event rules in Next-Gen SLAs
• Import/Export functionality now supports Next-Gen SLAs
• Cloning SLA feature is now available for Next-Gen SLAs
• SLA names are also displayed on top of the remaining duration in JSM Queues
• Next-Gen SLA fields can now be used in SLA notifiers
• Goals section in SLA definition has been redesigned for a better UX

Bug Fixes

• Problem when importing calendars with shared holidays
• Inconsistent labels for SLA Indicator values between the SLA Report and the Excel Export.
• Gadgets that are using deleted SLAs were malfunctioning.
• SLA panel and Time to SLA custom fields were showing inconsistent data in some cases
• Largest Span and All Cycles Calculations were miscalculating in some cases
• Lack of permission check for Resetting SLA over Rest API

New Features

• Migration Tool: Ability to migrate Legacy SLA configurations to Next-Gen SLAs
• Ability to define SLA notifier when SLA ends

Improvements

• Project, Issue Type, Components, Affected/Fixed versions, labels can now be used as event rules in Next-Gen SLAs
• Import/Export functionality now supports Next-Gen SLAs
• Cloning SLA feature is now available for Next-Gen SLAs
• SLA names are also displayed on top of the remaining duration in JSM Queues
• Next-Gen SLA fields can now be used in SLA notifiers
• Goals section in SLA definition has been redesigned for a better UX

Bug Fixes

• Problem when importing calendars with shared holidays
• Inconsistent labels for SLA Indicator values between the SLA Report and the Excel Export.
• Gadgets that are using deleted SLAs were malfunctioning.
• SLA panel and Time to SLA custom fields were showing inconsistent data in some cases
• Largest Span and All Cycles Calculations were miscalculating in some cases
• Lack of permission check for Resetting SLA over Rest API

• Next-Gen SLA calculation was problematic in some cases
• JQL input in the SLA definiton was not working correctly when the JQL contains special characters
• Dignostics report generation was not possible in some instances.

• Next-Gen SLA calculation was problematic in some cases
• JQL input in the SLA definiton was not working correctly when the JQL contains special characters
• Dignostics report generation was not possible in some instances.

Improvements

• Introduced optional thread types for Asynchronous Calculation: Fork Join Pool, Future Executors, Single Thread (more information)

Bug fixes

• Index replication problem (for specific DC instances) after re-generating SLA data.
• Gadgets were displaying disabled SLAs when they were configured to show “All SLAs”.
• Some instances were getting indexing errors.
• SLA Panel was showing inaccurate tooltip for succeeded SLAs.
• ‘Hide SLA name’ option was not working in CSV exports.
• SLAs with “All cycles” calculation method were not calculating paused duration accurately.
• Dynamic duration goal type was not working during SLA was in paused conditions.
• Deleting legacy SLAs was causing errors for some Jira instances.
• Creating default SLA goal empty was causing SLA calculation to fail

Improvements

• Introduced optional thread types for Asynchronous Calculation: Fork Join Pool, Future Executors, Single Thread (more information)

Bug fixes

• Index replication problem (for specific DC instances) after re-generating SLA data.
• Gadgets were displaying disabled SLAs when they were configured to show “All SLAs”.
• Some instances were getting indexing errors.
• SLA Panel was showing inaccurate tooltip for succeeded SLAs.
• ‘Hide SLA name’ option was not working in CSV exports.
• SLAs with “All cycles” calculation method were not calculating paused duration accurately.
• Dynamic duration goal type was not working during SLA was in paused conditions.
• Deleting legacy SLAs was causing errors for some Jira instances.
• Creating default SLA goal empty was causing SLA calculation to fail

New Features

• SLA History Tab Panel: see SLAs’ history in an issue (Next-Gen SLAs exclusive)
• JQL function: slaFunction isInCriticalZone() - search for issues which are in critical zone
• New SLA Goal Type: Next Business Day!
• Re-order SLA Panel: two new options for panel order - start date ascending/descending and custom (select which SLAs should be at the top/bottom)

Improvements

• SLA Indicator and SLA Overdue field’s indexing mechanism
• Next-Gen SLA listing page now has configurable table columns
• Caching SLA field values mechanism
• SLA Panel configuration page
• Set customer portal SLAs for all request types easily
• Gadgets support Next-Gen SLAs
• Elapsed percent is added to TTS custom fields’ groovy script usage

Bug Fixes

• Percent queries for SLAs with negotiation date
• SLA Reset function causing transitions to fail
• UI bugs in custom field configuration
• Completed SLA display bug custom field
• Reindexing errors
• Bug in SLA Report for Next-Gen SLAs
• Linked issue SLA
• SLA Config Item descriptions

New Features

• SLA History Tab Panel: see SLAs’ history in an issue (Next-Gen SLAs exclusive)
• JQL function: slaFunction isInCriticalZone() - search for issues which are in critical zone
• New SLA Goal Type: Next Business Day!
• Re-order SLA Panel: two new options for panel order - start date ascending/descending and custom (select which SLAs should be at the top/bottom)

Improvements

• SLA Indicator and SLA Overdue field’s indexing mechanism
• Next-Gen SLA listing page now has configurable table columns
• Caching SLA field values mechanism
• SLA Panel configuration page
• Set customer portal SLAs for all request types easily
• Gadgets support Next-Gen SLAs
• Elapsed percent is added to TTS custom fields’ groovy script usage

Bug Fixes

• Percent queries for SLAs with negotiation date
• SLA Reset function causing transitions to fail
• UI bugs in custom field configuration
• Completed SLA display bug custom field
• Reindexing errors
• Bug in SLA Report for Next-Gen SLAs
• Linked issue SLA
• SLA Config Item descriptions

• Diagnostics report generation was problematic in some instances
• slaFunction was not working in instances that have more than 1024 SLA definitions. It now respects the `jira.search.maxclauses` parameter of the Jira

• Diagnostics report generation was problematic in some instances
• slaFunction was not working in instances that have more than 1024 SLA definitions. It now respects the `jira.search.maxclauses` parameter of the Jira

New Features

• SLA Panels can now be configured to hide:
  • Completed SLAs
  • SLAs which are in non-working hours
  • Inactive SLAs.

Improvements

• Automation Integration module was causing massive logs.
• Diagnostics report now includes Time to SLA custom fields and their values which will decrease our support time.
• SLA Panel can now display separate icons to differentiate breaches within running and completed SLAs.

Bug fix

• Users who have project role permission were not able to see SLA Report under Project Reports section.
• Automation rules were failing in some instances due to invalid dependency configuration.
• SLA Report was displaying the previous cycles’ SLA End Date after the SLA was restarted.
• SLA Report was failing when Duration Input was in seconds.
• Import was failing in some instances.
• Reset SLA post function was allowing no SLA selection.

New Features

• SLA Panels can now be configured to hide:
  • Completed SLAs
  • SLAs which are in non-working hours
  • Inactive SLAs.

Improvements

• Automation Integration module was causing massive logs.
• Diagnostics report now includes Time to SLA custom fields and their values which will decrease our support time.
• SLA Panel can now display separate icons to differentiate breaches within running and completed SLAs.

Bug fix

• Users who have project role permission were not able to see SLA Report under Project Reports section.
• Automation rules were failing in some instances due to invalid dependency configuration.
• SLA Report was displaying the previous cycles’ SLA End Date after the SLA was restarted.
• SLA Report was failing when Duration Input was in seconds.
• Import was failing in some instances.
• Reset SLA post function was allowing no SLA selection.

• elapsedPercentage and remainingPercentage JQL functions were working incorrectly for some SLA definitions (re-indexing is not necessary to fix the problem)
• Elapsed and paused duration calculations were not made according to the working calendar for Next Generation SLAs.

• elapsedPercentage and remainingPercentage JQL functions were working incorrectly for some SLA definitions (re-indexing is not necessary to fix the problem)
• Elapsed and paused duration calculations were not made according to the working calendar for Next Generation SLAs.

The future of SLA management is here…

Enhanced SLA Configuration 💪

• Regenerate entire SLAs anytime, even for issues created before an SLA was configured.
• Field value conditions such as the ability to pause an SLA when the assignee field is empty.
• Multiple start/stop conditions.
• Set multiple goals in a single SLA.
• Combine an unlimited number of status, field, date and comment options.

Improved Performance 🏃

• We’ve upgraded our system to incremental calculations which has less impact on issue transition and edit durations.

Brand New Design

• A more compact and easy-to-use design.
• Control all start, stop, reset and pause conditions, plus goals in a single page.

This is a backwards compatible release, meaning you will have the option between the legacy configuration (where everything will be exactly the same as v. 9.8.4) and the new Next-Gen SLAs (BETA). We look forward to hearing your feedback and building the next generation of SLA management together! Find documentation here.

The future of SLA management is here…

Enhanced SLA Configuration 💪

• Regenerate entire SLAs anytime, even for issues created before an SLA was configured.
• Field value conditions such as the ability to pause an SLA when the assignee field is empty.
• Multiple start/stop conditions.
• Set multiple goals in a single SLA.
• Combine an unlimited number of status, field, date and comment options.

Improved Performance 🏃

• We’ve upgraded our system to incremental calculations which has less impact on issue transition and edit durations.

Brand New Design

• A more compact and easy-to-use design.
• Control all start, stop, reset and pause conditions, plus goals in a single page.

This is a backwards compatible release, meaning you will have the option between the legacy configuration (where everything will be exactly the same as v. 9.8.4) and the new Next-Gen SLAs (BETA). We look forward to hearing your feedback and building the next generation of SLA management together! Find documentation here.

Improvements

• SLA Notifier now can publish events in EventBundle format allowing some other plugins which does not accept default IssueEvent format to be integrated with Time to SLA notification system (Such as Automation for Jira)

• Some of the notifications were temporarily disabled if there were both Slack and mail notifications on a single SLA
• Time to SLA custom field was causing "Cannot retrieve Timestamp methods due to security restrictions" warnings in logs
• Time to SLA trigger in Automation for Jira plugin was causing redundant errors in logs

Improvements

• SLA Notifier now can publish events in EventBundle format allowing some other plugins which does not accept default IssueEvent format to be integrated with Time to SLA notification system (Such as Automation for Jira)

Bug fixes

• Some of the notifications were temporarily disabled if there were both Slack and mail notifications on a single SLA
• Time to SLA custom field was causing "Cannot retrieve Timestamp methods due to security restrictions" warnings in logs
• Time to SLA trigger in Automation for Jira plugin was causing redundant errors in logs

• TTS Permission page was not reachable in some instances.
• Users were not able to save reports that uses JQL.
• Updating TTS from versions prior to 9.6.2 was taking too long.

• TTS Permission page was not reachable in some instances.
• Users were not able to save reports that uses JQL.
• Updating TTS from versions prior to 9.6.2 was taking too long.

SLA Order custom fields were not created automatically in some instances

SLA Order custom fields were not created automatically in some instances

New Features:

• Ordering issues by SLA is now available. Note: This feature requires re-index. Click here to find out more.
• Now you can use “SLA threshold breached” trigger in Automation for Jira plugin for your SLAs. Click here for details.

Improvements

• You can now use a JQL query to get SLA report as well as saved search filters.
• It is now possible to add multiple reset SLA post functions.

Bug Fixes

• Reset SLA post function was not working in some cases where All SLAs is selected.
• Users were getting “AJS.Meta.getLanguage is not a function” error in deprecated Jira 7 versions.

New Features:

• Ordering issues by SLA is now available. Note: This feature requires re-index. Click here to find out more.
• Now you can use “SLA threshold breached” trigger in Automation for Jira plugin for your SLAs. Click here for details.

Improvements

• You can now use a JQL query to get SLA report as well as saved search filters.
• It is now possible to add multiple reset SLA post functions.

Bug Fixes

• Reset SLA post function was not working in some cases where All SLAs is selected.
• Users were getting “AJS.Meta.getLanguage is not a function” error in deprecated Jira 7 versions.

Some UI features were broken for specific languages

Some UI features were broken for specific languages

New Features

• Slack notifications have been added to the existing notifier function.
• Remaining percentage notifications have also been added. Now users can get notified via email and Slack when a set percentage of an SLA has passed.
• Group custom field selection has been added to enable users to select an entire group(s) to receive SLA notifications.

Improvements

• CDN Compatibility for Data Center instances has been made.
• Development of the SLA Reset Post Function which was slowing down in some instances.
• TTS Issue Menu visibility permission has been added.

Bug Fixes

• Reset SLA issue operation was not working in some instances.

New Features

• Slack notifications have been added to the existing notifier function.
• Remaining percentage notifications have also been added. Now users can get notified via email and Slack when a set percentage of an SLA has passed.
• Group custom field selection has been added to enable users to select an entire group(s) to receive SLA notifications.

Improvements

• Development of the SLA Reset Post Function which was slowing down in some instances.
• TTS Issue Menu visibility permission has been added.

Bug Fixes

• Reset SLA issue operation was not working in some instances.

New Features

• “System-wide asynchronous SLA calculation”Effective way to offload all SLA calculation overhead on background tasks. Enabling “System-wide asynchronous SLA calculation” results in the same behavior as making all SLA definitions asynchronous individually, but offers an improved performance since there is no need to check each SLA definition one by one. Designed for big Jira instances with many SLA definitions. Note that this feature offers a significant performance boost but at a cost of small delay (~1 minutes) on SLA updates. You can enable it in Time to SLA Menu > Settings > General settings

Improvements

• SLA Panel now can be placed on top of right sidebar in the issue view. You can switch SLA panel position at Time to SLA menu > SLA Panel

New Features

• “System-wide asynchronous SLA calculation”Effective way to offload all SLA calculation overhead on background tasks. Enabling “System-wide asynchronous SLA calculation” results in the same behavior as making all SLA definitions asynchronous individually, but offers an improved performance since there is no need to check each SLA definition one by one. Designed for big Jira instances with many SLA definitions. Note that this feature offers a significant performance boost but at a cost of small delay (~1 minutes) on SLA updates. You can enable it in Time to SLA Menu > Settings > General settings

Improvements

• SLA Panel now can be placed on top of right sidebar in the issue view. You can switch SLA panel position at Time to SLA menu > SLA Panel

New Feature

• Designed the Time to SLA landing page which will guide through the main features.

Improvements

• Time to SLA export file can now downloaded directly through the browser.
• Time to SLA’s issue menu can now be restricted to issues by JQL.
• SLA panel handles expired sessions in a better way.

Bug Fixes

• When there are more than 100 request types in a single Service Desk project only 100 of them were being displayed in customer portal SLAs.
• In some particular cases, SLA Overview tab panel was causing errors.
• ‘Where is my SLA’ was not functioning when priority was disabled for the project.
• Accidentally leaving JQL with space character(s) was causing SLA not to be calculated or tracked.
• For some cases, resetting SLA through issue menu was causing inaccurate SLA reset dates.
• Multiple SLA resets were not clearing elapsed and remaining times.
• SLA Notifier was not functioning in some cases.
• Custom fields’ were not respecting SLA selection configuration in rare cases.

New Feature

• Designed the Time to SLA landing page which will guide through the main features.

Improvements

• Time to SLA export file can now downloaded directly through the browser.
• Time to SLA’s issue menu can now be restricted to issues by JQL.
• SLA panel handles expired sessions in a better way.

Bug Fixes

• When there are more than 100 request types in a single Service Desk project only 100 of them were being displayed in customer portal SLAs.
• In some particular cases, SLA Overview tab panel was causing errors.
• ‘Where is my SLA’ was not functioning when priority was disabled for the project.
• Accidentally leaving JQL with space character(s) was causing SLA not to be calculated or tracked.
• For some cases, resetting SLA through issue menu was causing inaccurate SLA reset dates.
• Multiple SLA resets were not clearing elapsed and remaining times.
• SLA Notifier was not functioning in some cases.
• Custom fields’ were not respecting SLA selection configuration in rare cases.

• SLA Panel was not taking calendar business hours in a day into consideration when formatting durations
• SLA Pie Chart was not displaying any results when SLA selection left empty
• Selected included SLAs in the custom fields configurations prior to version 9.1.0 were not taken into consideration

• SLA Panel was not taking calendar business hours in a day into consideration when formatting durations
• SLA Pie Chart was not displaying any results when SLA selection left empty
• Selected included SLAs in the custom fields configurations prior to version 9.1.0 were not taken into consideration

New Features

• Long awaited dynamic countdowns added to SLA panel
• New JQL functions now accept SLA names as parameters

Improvements

• Service Desk comment visibility is now fully supported with SLA start/end conditions
• More issue fields added to SLA Reset options
• SLA dates fields will be cleared once related SLAs are invalidated

Bug Fixes

• Some changes on SLAs were not reflected on the configuration page even though they have been saved successfully
• On some rare occasions SLA panel and Time to SLA Custom Field display inconsistent information
• UTF-8 is forced on SLA Import/Export module so that it also works well on systems with missing encoding parameter

New Features

• Long awaited dynamic countdowns added to SLA panel
• New JQL functions now accept SLA names as parameters

Improvements

• Service Desk comment visibility is now fully supported with SLA start/end conditions
• More issue fields added to SLA Reset options
• SLA dates fields will be cleared once related SLAs are invalidated

Bug Fixes

• Some changes on SLAs were not reflected on the configuration page even though they have been saved successfully
• On some rare occasions SLA panel and Time to SLA Custom Field display inconsistent information
• UTF-8 is forced on SLA Import/Export module so that it also works well on systems with missing encoding parameter

Periodic Met vs Exceeded Issues chart was not showing any data in some cases

Periodic Met vs Exceeded Issues chart was not showing any data in some cases

Periodic Met vs Exceeded SLA gadget was not showing any data when Target Date is selected as include option

Periodic Met vs Exceeded SLA gadget was not showing any data when Target Date is selected as include option

WARNING! THIS UPDATE BRINGS INDEX BASED GADGET CALCULATIONS. IF YOU HAVE NOT REINDEXED YOUR SYSTEM AFTER TIME TO SLA 9.X UPDATE PLEASE DO IT BEFORE UPDATING. FOR DETAILS PLEASE SEE THIS GUIDE.

Improvements:

• SLA Gadgets now work with Lucene indexes. They now return results up to 10 times faster!
• Settings page is redesigned

Bug Fixes:

• Invalidated SLAs were wrongly indexed.
• Export functionality were not working for some instances.
• Searching with calendar ID was not available in the SLA Search REST service.

WARNING! THIS UPDATE BRINGS INDEX BASED GADGET CALCULATIONS. IF YOU HAVE NOT REINDEXED YOUR SYSTEM AFTER TIME TO SLA 9.X UPDATE PLEASE DO IT BEFORE UPDATING. FOR DETAILS PLEASE SEE THIS GUIDE.

Improvements:

• SLA Gadgets now work with Lucene indexes. They now return results up to 10 times faster!
• Settings page is redesigned

Bug Fixes:

• Invalidated SLAs were wrongly indexed.
• Export functionality were not working for some instances.
• Searching with calendar ID was not available in the SLA Search REST service.

New Features:

• 
Long-awaited Export/Import functionality is added to the app.
• Undo Reset SLA: You can now clear previous reset actions from Time to SLA issue menu.

Improvements:

• Showing linked issue’s SLAs for custom fields functionality is improved.

Bug Fixes:

• SLA Panel was not loading to customer portal in some cases.
• isBreached() function was not returning paused and breached SLAs.

New Features:

• 
Long-awaited Export/Import functionality is added to the app.
• Undo Reset SLA: You can now clear previous reset actions from Time to SLA issue menu.

Improvements:

• Showing linked issue’s SLAs for custom fields functionality is improved.

Bug Fixes:

• SLA Panel was not loading to customer portal in some cases.
• isBreached() function was not returning paused and breached SLAs.

Improvements

• Diagnostics report now includes notification information
• Corrupted scheduled task controls added to Time to SLA integrity checker

Bug Fixes

• A minor performance problem related with JQL field in SLA configuration is fixed
• Time to SLA, Overdue, Indicator and SLA Dates fields were not configurable for multiple contexts
• Notification dates were calculated wrong in some cases

Improvements

• Diagnostics report now includes notification information
• Corrupted scheduled task controls added to Time to SLA integrity checker

Bug Fixes

• A minor performance problem related with JQL field in SLA configuration is fixed
• Time to SLA, Overdue, Indicator and SLA Dates fields were not configurable for multiple contexts
• Notification dates were calculated wrong in some cases

• Date custom field labels were not displayed correctly in SLA configuration page
• A false warning was seen in application logs due to redundant resource file

• Date custom field labels were not displayed correctly in SLA configuration page
• A false warning was seen in application logs due to redundant resource file

Improvement:

• Now it is possible to control visibility of Time to SLA menu in issue view with JQL parameter

Bug Fixes:

• Fixed duplicate SLA problem that has been seen in some cases
• Exclude SLA option for SLA panel was not working
• Minor bug fix in Service Desk SLAs configuration page

Improvement:

• Now it is possible to control visibility of Time to SLA menu in issue view with JQL parameter

Bug Fixes:

• Fixed duplicate SLA problem that has been seen in some cases
• Exclude SLA option for SLA panel was not working
• Minor bug fix in Service Desk SLAs configuration page

• “Some SLAs” option was not working properly for Customer Portal SLAs
• Tooltip messages were broken in SLA panel

• “Some SLAs” option was not working properly for Customer Portal SLAs
• Tooltip messages were broken in SLA panel

Duration functions were not working as expected in some cases

Duration functions were not working as expected in some cases

• Permission check for SLA regeneration in SLA configuration screens was missing
• Negative overdue durations displayed for non-breached SLAs with negotiation goal
• Percentage calculations were wrong for SLA with negotiation date goal when there is paused duration into issue
• Percentage search was not working correctly for SLAs with negotiation date goal
• Non-breached SLAs with negotiation date goals were displayed in breach duration searches
• Filters in SLA configuration page was not working on Jira8 instances

• Permission check for SLA regeneration in SLA configuration screens was missing
• Negative overdue durations displayed for non-breached SLAs with negotiation goal
• Percentage calculations were wrong for SLA with negotiation date goal when there is paused duration into issue
• Percentage search was not working correctly for SLAs with negotiation date goal
• Non-breached SLAs with negotiation date goals were displayed in breach duration searches
• Filters in SLA configuration page was not working on Jira8 instances

• New SLA Search: Easy to use, blazing fast SLA Search. Find details here.
• SLAs can now be displayed in Jira Service Desk customer portal and Jira Software boards. Find details here.
• Special custom field to utilize SLA information trough eazyBI. Find details here.
• Where is my SLA?: One click inspection tool for troubleshooting missing SLAs on issues. Find details here.

• New SLA Search: Easy to use, blazing fast SLA Search. Find details here.
• SLAs can now be displayed in Jira Service Desk customer portal and Jira Software boards. Find details here.
• Special custom field to utilize SLA information trough eazyBI. Find details here.
• Where is my SLA?: One click inspection tool for troubleshooting missing SLAs on issues. Find details here.

• SLA panel was not displaying SLA durations correctly
• A minor misconfiguration was causing lots of warnings in application logs
• SLA Panel was not displayed in some cases

• SLA panel was not displaying SLA durations correctly
• A minor misconfiguration was causing lots of warnings in application logs
• SLA Panel was not displayed in some cases

• SLA panel was not displaying SLA durations correctly
• A minor misconfiguration was causing lots of warnings in application logs
• SLA Panel was not displayed in some cases