Since upgrading to v1.11.0-rc1 the ticket owner does not receive any ticket information regarding updates sent by customer. I checked email addresses, notification settings and tried different combinations. All other notifications work as always, for example internal updates etc. This issue was since the very beginning of the upgrade, so I assume it's not a configuration problem on my side. ServerinformationenosTicket-Versionv1.11.0-rc1 (e321982) —  AktuellServer-SoftwareApache/2.4MySQL-Version10.1.35PHP-Version5.6.37

As a reminder, 1.11.0rc1 is a Release Candidate (BETA software) and should not be used in a production environment.  It was released for people to test it.How do you have email setup?  (Phpmail or SMTP)If you have it setup via PhpMail please change to SMTP and see if it fixes the issue.

Tried Phpmail and SMTP. Both work fine, but still no notification to the ticket owner nor anybody else when a customer message is added. All other notifications are working well. 

Do you have them turned on?Admin panel -> Settings -> Tickets -> Autoresponder (for users)andAdmin panel -> Settings -> Tickets -> Alerts and Notices (for Agents)

I checked again the settings, the autoresponder are activated and so are the alerts and notification. The system does as expected for all notifications except for the "new message alert", non of the possible recipients is getting an alert when customers ads a new message.  

Maybe its a bug in 1.11.0-rc1.  Works fine in the current stable 1.10.4

5 days later

Uhm, any chance to downgrade to the stable version? Did not find any information about that. 

There is no downgrade path.  You would restore your DB and site from backup.Or you would start a new DB and lose any data that is in the old one.

ok thanks, will restore stable installation

So, does that mean this is a known and accepted bug that will be dealt with before final release?

@[deleted] @[deleted] @[deleted]Please use the latest pull from `develop-next` branch as we have addressed a LOT of issues since the initial release of the release candidate.Cheers.

I had to restore my version from a backup - we also had problems with rules that would sort and auto assign tickets to depts. ect. Is there a list of issues that have been corrected in the 'develop-next' branch....?I realise that these are beta release but I have never had an issue with a beta release of OSTicket that cant be ignored. This was the first time I had to restore.Keep up the good work guys, we all appropriate it!

please someone to help me I have the stable version but do not send mail to the owner of the ticket (auto-reply new ticket) everything is configured. I have reviewed all the suggestions and I do not want to have to reinstall.Versión osTicketv1.10.4 (035fd0a) —  Hasta la fechaServidor del Software WebApacheVersión MySQL5.5.54Versión PHP5.4.34Extensiones PHPgdlib Utilizado para la manipulación de imagen e impresión en PDFimap Usado para la recuperación del Emailxml API XMLxml-dom Utilizado para el procesado de Email en HTMLjson Mejora el desempeño de creación y el procesamiento JSONmbstring Altamente recomendado para el contenido en idiomas europeos que no sean del oestephar Altamente recomendao para los paquetes de idioma y complementos

@[deleted] please open your own thread.

@[deleted]LOLIf we did...it'd be a mile long... you can simply compare develop (1.10.x) to develop-next (1.11.x) and see all the commits added (500+ commits). Good luck ;)Cheers.

To answer my own, question, yes. . .  and it looks like it is fixed in develop-next / 1.11.x

7 days later

Awesome I look forward to the next release....

Write a Reply...