opened 05:14AM - 22 Nov 18 UTC
closed 07:51AM - 30 Aug 21 UTC
bug
verified
<!--
Hi there - thanks for filing an issue. Please ensure the following things … before creating an issue - thank you! 🤓
Since november 15th we handle all requests, except real bugs, at our community board.
Full explanation: https://community.zammad.org/t/major-change-regarding-github-issues-community-board/21
Please post:
- Feature requests
- Development questions
- Technical questions
on the board -> https://community.zammad.org !
If you think you hit a bug, please continue:
- Search existing issues and the CHANGELOG.md for your issue - there might be a solution already
- Make sure to use the latest version of Zammad if possible
- Add the `log/production.log` file from your system. Attention: Make sure no confidential data is in it!
- Please write the issue in english
- Don't remove the template - otherwise we will close the issue without further comments
- Ask questions about Zammad configuration and usage at our mailinglist. See: https://zammad.org/participate
Note: We always do our best. Unfortunately, sometimes there are too many requests and we can't handle everything at once. If you want to prioritize/escalate your issue, you can do so by means of a support contract (see https://zammad.com/pricing#selfhosted).
* The upper textblock will be removed automatically when you submit your issue *
-->
### Infos:
* Used Zammad version: 2.7.0
* Installation method (source, package, ..): source
* Operating system: ubuntu 18.04
* Database + version: mariadb
* Elasticsearch version: -
* Browser + version: chrome latest
### Screenshot:

### Expected behavior:
* Current time: 6 am
* Warten auf Erinnerung: Yesterday, ~5pm
* Notification: ~5 hours ago
### Actual behavior:
* Notification: ~13 hours ago
Yes I'm sure this is a bug and no feature request or a general question.
I’m creating the topic upon suggestion of @anon29869905 .
It looks now slightly different to the github issue.
Infos:
Used Zammad version: 2.7.0
Installation method (source, package, …): source
Operating system: ubuntu 18.04
Database + version: mariadb
Elasticsearch version: -
Browser + version: chrome latest
Expected behavior:
No nightly escalation email
Actual behavior:
Nightly excalation emails roughly at 0am UTC
Steps to reproduce the behavior:
Create a ticket
Set “Warten bis” to 4pm
Expect a notificaiton email at roughly 4pm localtime (=OK)
Additional emails arrive at 0am UTC
Same is true for zammad notifications
Hey,
as far as I’m aware you currently can’t disable those notifications.
The only way to “disable” them is to disable your E-Mail-Notification for escalated E-Mails (or) work your reminders away, before Zammad can bug you with it’s reminder.
For this you could use a trigger (or scheduler) that runs at about let’s say 10-11pm UTC that resets all pending reminders reached back to open or another own custom state.
Thanks a lot for your suggestions. I don’t think they’ll work out for us, but thank you anyway.
system
Closed
March 23, 2019, 1:48pm
4
This topic was automatically closed 120 days after the last reply. New replies are no longer allowed.