--- title: "(07.2021-03.2024) Release history" canonical: "https://support.appfire.com/space/TTS/46728221/(07.2021-03.2024)%20Release%20history" format: markdown --- > Macro (aura-html) This page lists the release notes for every production version of Time to SLA for Jira. ### 10.14.6-AC-2024-03-08 - Added ‘Report Scope Limit' feature, enabling Time to SLA admins to set a maximum limit on the number of issues included in the SLA Report. ### **10.14.5-AC-2024-02-12** - Improved the percentage display of exceeded SLAs, focusing on Next Business Day (NBD) targets and negotiation date goals. - Resolved an issue causing Null Pointer Exceptions (NPE) on the SLA Reports page. - Addressed a functionality issue with JQL 3.0, where the join feature was not working as expected. - Integrated a feature to redirect built-in reports to the new SLA Reports page. - Responding to user feedback, we've added the capability for users to view SLA goals directly on the report. ### **10.14.4-AC-2023-01-12** - Removed Time to SLA Search 3.0 custom fields from the SLA Report field selection. ### **10.14.3-AC-2023-12-20** - Bug Fixes - Resolved an issue where an SLA with JQL and Diagnostics REST API was causing a "recursively defined member" error. - Fixed an issue where the app generated a report upon clicking the filter. - Corrected the display of the "%" symbol, ensuring it appears after the number. ### **10.14.2-AC-2023-10-21** - Bug Fixes - Resolved an issue where clicking “Filter” was generating a report. - Fixed a bug on the Reports page that was displaying an error. - Addressed the Infinite Recursion Exception caused during SLA report generation. - Fixed an error in Issue SLA Rest that was throwing a "`Recursively Defined Member`" error. - Resolved an issue where SLA Configuration could not be created for some instances. - Removed unnecessary error logs. ### **10.14.1-AC-2023-10-17** - Bug Fixes - Server to Cloud (JCMA) migration was getting stuck at 20%. - SLA Report was failing in some scenarios. - There were cases of data corruption within migrated report filters. - Some users were not able to enable TTS in Jira 9.11. - Select and multi-select custom field values were not showing up on the SLA Report. ### **10.14.0-AC-2023-09-22** New Features: - Introducing a brand new SLA report UI with enhanced functionalities, including "Background Report" and "Periodic Report." - Now offering the ability to utilize Time to SLA custom fields in Data Pipeline exports. Improvements: - Ability to use ‘customFieldManager’ in SLA Notifier templates. ### **10.13.5-2023-08-21** Minor Fixes: - Renamed the page for muting SLA notifications. - Fixed an issue where autocomplete suggestions were returning null for CRT (Custom Report Type) in JQL (Jira Query Language). - Made text adjustments on the TTS Server Permission Page. Bug Fixes: - Resolved an issue where the TTS custom field was falsely marked as exceeded when it was not. ### **10.13.4-2023-04-04** Bug Fixes: - JCMA migration was not working - 10.13.3 version was failing to initialize in some DB types. ### **10.13.3-2023-02-30** Bug Fixes: - 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. ### **10.13.2-2023-02-20** 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. ### **10.13.1-2023-01-31** Bug Fix - 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. ### **10.13.0-2022-12-20** 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. ### **10.13.0-2022-12-19** With this version, the Time to SLA JQL 2.0 functions have been removed. You can use [this documentation](https://appfire.atlassian.net/wiki/spaces/TTS/pages/49775011) to learn more about JQL 3.0 functions and [this documentation](https://appfire.atlassian.net/wiki/spaces/TTS/pages/49775289) 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. ### **10.12.1-2022-12-06** - Customers using Oracle DB had problems sending notifications. - Calendar import didn't work in some cases. ### **10.12.0-2022-10-19** - New Features - Ability to mute SLA notifications for a single issue or issues within a JQL filter has been added. - 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. ### **10.11.2-2022-08-19** - Calendar fetch errors have been eliminated. - 'No Target' goal type problem, which was causing failures in unexpected places, has been fixed. ### **10.11.1-2022-08-02** - 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. ### **10.11.0-2022-07-19** - 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. ### **10.10.0-2022-06-07** - ​Ability to exclude finished SLAs from regeneration tasks has been added. - Additional SLA Date JQL functions such as startOfYear and endOfMonth have been added. - 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. - 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. - SLA Panel was refreshed when the “watch external issue changes” option was disabled in some cases. - SLA Date parameters in SLA Notifier was not accounting for the calendar of an SLA. ### **10.9.1-2022-04-12** - JCMA integration was not working correctly. - Business Hours have been added to the eazyBI custom field. ### **10.9.0-2022-03-18** - SLA History tab panel can be exported to Excel/PDF. - TTS Date Custom Field searcher has been added. - Some messages in French and German were incorrect. - SLA recalculation was not working in some instances. - Third-party JQL functions were not successfully executed within the 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. ### **10.8.1-2022-02-17** - Some migration scope was missing causing no migration to be found. ### **10.8.0-2022-02-11** - Added JCMA support. Migrating to the Cloud is now easier than ever. Simply include the Time to SLA in your migration. - The Escalation Service was not running properly in some cases. - ‘Elapsed Percentage’ showed an error when the SLA end date was before the SLA start date. - All SLAs inclusion was causing issues with CMJ integration. - The ‘Is Over’ notification trigger was not working properly. - SLA Dates custom fields were showing dates of SLAs that haven’t started yet. - 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. ### **10.7.0-2021-10-22** - Integration with Configuration Manager for Jira: Now you can export/import TTS custom fields, SLAs, settings, gadgets, report configurations, etc. via CMJ. ### **10.6.2-2021-10-16** **Notice:** Starting with this version, Legacy SLAs will be migrated automatically. Update your Time to SLA and let it take you to the next level! - 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. - Improved cache mechanism. - Calendar date formats are now aligned with Jira Look and Feel. - 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. ### **10.6.1-2021-10-11** - SLA Migration was finishing before all SLAs are migrated in some instances. - Postponed Event Checker Scheduled Task was causing slowdowns in some instances. ### **10.6.0-2021-10-01** **Notice:** Starting with this version, Legacy SLAs will be migrated automatically. Update your Time to SLA and let it take you to the next level! - 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. - 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. ### **10.5.2-2021-09-23** - The Migration Tool was not working in some instances. - Importing SLAs with the default goal was not working. ### **10.5.1-2021-09-07** - SLA Notifiers can now be configured to have percentages greater than 100%. - Jira Users, Voters and Watchers can now be used in SLA Notifiers. - 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. ### **10.5.0-2021-08-14** - You can now import SLAs from JSM with just a few clicks ([more information](https://confluence.snapbytes.com/x/GgumAw)). - Ability to join SLA JQL functions ([more information](https://confluence.snapbytes.com/time-to-sla/sla-search/sla-search-3-0-jql-functionalities)). - An SLAs configuration can now included via REST API ([more information](https://documenter.getpostman.com/view/15299464/Tzsfn5ju)). - Next-Gen SLAs' email notifiers now support CC and BCC. Email preview option has also been introduced. - The calendar page has been re-engineered. - The SLA configuration page has been visually improved. - Start/Stop/Reset conditions now support multiple cycles. - You can now stop a notifier after a specified number of occurrences. - The 'Time to SLA' custom field was showing inaccurate SLA duration for Next-Gen SLAs. - Saved SLA reports were not listed in some cases. - The 'Get SLA details' REST service was not returning a result for Next-Gen SLAs. - External issue changes were causing all SLAs to be displayed in the JSM customer view, even when they were not configured as seen. - Searching for SLA Indicator's 'PROGRESS' state was erroneous if there were SLAs with MET state. - The SLA History tab panel was displaying recursive Start/Stop events. - SLA Search 3.0 was erroneous for migrated SLAs. - The remaining duration calculation for SLAs which had been paused in previous cycles was inaccurate. - Disabled Slack notifiers were still sending notifications. - The SLA History panel was not displaying the correct state for the stop events. - The SLA Clone was not cloning Pause conditions. - Slack Notifiers were not migrating to Next-Gen correctly. - Notifiers with 0m were not migrating to Next-Gen correctly. ### **10.4.1-2021-07-05** - You can now search issues for particular SLAs. - Warning dialog shows up if there are unsaved changes on the SLA configuration page. - 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.