Release notes

Freshdesk Release Notes - June 2023

Related products: Freshdesk
Freshdesk Release Notes - June 2023

New Features and Enhancements

 

All Below features and enhancements are available to all customers from June 30, 2023.

 

Date-time format auto conversion in Freshdesk

Customize the date and the time format for every agent under agent portal settings. The date-time format is updated automatically when you set the global language for your helpdesk.

More details here.

YcxY694LOnP5U9-5DejEIEzqF5nIZnUofxiQKrfMXfZr6Zx87p4EtXj1wjD0b6dfDksr-u5tkkbY91ZCFb0iT3aUaDR3lbHVdYJbi5uKsa_z7Hmk00xLeZAmZ8MVv5sptvtHz6BAnG93r6J6B8W0KxA


 

HTML code editor for email notifications template in Freshdesk

Customize the outgoing email template for every type of email notification by adding the HTML & CSS code to the email notifications template.

More details here.

TbRcDT1w4azmJD3zc8f-It0LNUzZ7pQQf5CYtRQvMaZgaSEA2z50CZoZOA06uSWtnAUfJ-Na4EDwXGMzx6P2DG-t7206HI6JlITzkwXh6ipXWMi_fW1rrYy7fA22vgPt1b0EHpHeonfQkRSRINRbKs4

 

Google Analytics 4 upgrade impact on Freshdesk apps

On July 1, 2023 all standard Universal Analytics (UA) properties have stopped processing data. It's critical to migrate UA property settings to Google Analytics 4, or you will begin to lose data.

More details here.

U9UlulTspRfolgScxaf-_mEQmK-iZGB2aeAg9alU9AL01w7iP7mXyB0DPsDOmyz-NaD9-XgiLrdehOVGIuxn1ZzkbggvpXAnFrcRrqHAdSCeMX883CO7gbkTFugE9kI3Bz3ZHGKWO_vGDQAthAbgdFo

 

Harvest app  auth changes in Freshdesk

Harvest is deprecating V1 APIs completely by end of 2023 and will only support V2 APIs. V2 APIs require 2FA and will not work with Basic Auth. Please switch to 2FA and update the Harvest app for continued usage.

More details here.

78UbaB6goUcxO7ZwZHYVVioBzlZSm021ddH7JMr9NhlND_YP0-ewmlkNJICNVL6twz5UGFcNTYjfbmrp5hRgIZiqzcvi53-EiMf4mD4OSQuV-sSeTzAXdFYo9pt08rGHzxeZGOVvZ-AL6hQQgY6b4d4

 

Ticket filter in iOS Freshdesk App

Filter tickets on the iOS mobile app on the fly. Use default filters or custom drop-down fields to search for specific list of tickets.

More details here.

Bd5wXjC6RMhy50Ha7ra4FS79I_pMgntBO1apQaAYtA9612UhH3AVW3tMqUx45Gd7kiVgDtVb8iSWZu4olzsTu4xh6O_l1pS4_5VZrp3SQY83RmHljzpUeqUlt4jnhrOK5zmrEDyHchmtsvf0m5VLC7c

 

Bug fixes

 

These were the bugs detected, and they’ve now been fixed.

  1. Single line & multi-line text fields were not retained on archiving the ticket.
  2. Ticket creation time was displayed incorrectly when an agent tried to merge two tickets.
  3. Contacts import email delivery failed when the profile language was non-English.
  4. Canned responses failed to load for agents on the tickets page when many canned responses were configured.
  5. The ‘Merge’ button was not visible in the Parent ticket.
  6. Agents were unable to log in using SSO in sandbox accounts.
  7. Customers were able to toggle ON the Freddy AI features multiple times when logged in from different browsers.
  8. Average Handling Time (AHT) was enabled in the production account when customers tried enabling other features in the sandbox account.
  9. The time of ticket creation was displayed wrongly due to daylight saving savings time.
  10. There was a mismatch in the data displayed in the dashboard widget and drill-down data.
  11. The values under the custom ticket dropdown field were not displayed in alphabetical order in the customer portal.
  12. The video on the threads feature was not working.
  13. End users were unable to log in to the customers’ portal unless the 'Remember me on this computer' checkbox was checked.
  14. Automation rules set up based on SLA violations were not executed.
  15. Attachments were not included when automation for forwarding as a thread was configured.
  16. The email field options (From, To, CC, BCC) were not visible when customers tried to forward a thread.
  17. The First Response Due tag was not shown on tickets even though the first response time was breached.
  18. The help widget did not load properly on the customer portal.
  19. There were issues with the images in the signature when printing the ticket.
  20. Tickets were assigned to agents who only had view access.

Cheers! 

Join the Community or User Group to Participate in this Discussion