Submit a ticketCall us

WebinarUpcoming Webinar: Should I Move My Database to the Cloud?

So you’ve been running an on-premises SQL Server® for a while now. Maybe you’ve moved it from bare metal to a VM, and have seen some positive benefits. But, do you want to see more? If you said “YES!”, then this session is for you, as James Serra will review the many benefits that can be gained by moving your on-prem SQL Server to an Azure® VM (IaaS). He’ll also talk about the many hybrid approaches, so you can gradually move to the cloud. If you are interested in cost savings, additional features, ease of use, quick scaling, improved reliability, and ending the days of upgrading hardware, this is the session for you.

Register now.

Home > Success Center > Web Help Desk (WHD) > WHD - Knowledgebase Articles > Tickets in Resolved status do not auto-close

Tickets in Resolved status do not auto-close

Table of contents

Updated November 15, 2017

Overview

Tickets set to Resolved status remain in the Resolved state and do not auto-close when the ticket reaches the auto-close time set in the Resolved status setting (for example: Automatically Close Ticket After 1 minute). The ticket should change to Closed status and enable Web Help Desk to send a survey to the client.

This issue only impacts instances with MySQL and Microsoft® SQL Server® database on the backend. Tickets work as expected on PostgreSQL.

 

Environment

  • WHD 12.5.1
  • MySQL
  • Microsoft SQL Server

Detail

Download Web Help Desk 12.5.2 from the Customer Portal and install the service release in your deployment. See the Release Notes and the Web Help Desk Upgrade Guide for additional details and procedures for this upgrade.  

 

 

Last modified

Tags

Classifications

Public