Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feat.] Timezone selector #54

Open
WEBudoGT opened this issue Apr 13, 2023 · 5 comments
Open

[Feat.] Timezone selector #54

WEBudoGT opened this issue Apr 13, 2023 · 5 comments

Comments

@WEBudoGT
Copy link

Is your feature request related to a problem? Please describe.
Notification body including timestamps will always produce them in server's timezone (GMT in my case).

Describe the solution you'd like
As notification body is based on the same "EmailNotification Template", and Email notifications are timezone configurable, I guess a dropdown with timezone selector could be possible to implement.
It would be great to have this option.

@irgendwr
Copy link
Owner

Hi, thanks for the suggestion!

This is a duplicate of #49, which was closed because there was no activity. I welcome anyone to contribute this feature, but I currently don't have the time and interest to add any new features myself.

@irgendwr
Copy link
Owner

I will implement this in exchange for a pizza 🍕 ;)

@kklp90
Copy link

kklp90 commented Nov 19, 2024

@irgendwr i used rule and pipeline to create new timestamp field which correct with my timezone in the message. But when notifying via Telegram, there is no content of this field.

time

@irgendwr
Copy link
Owner

@kklp90 does it work if you try it with an email notification?

@kklp90
Copy link

kklp90 commented Nov 22, 2024

@irgendwr i got working it with telegram now. In the template message, it must be ${message.fields.newtime} instead of ${message.newtime}. That is a workaround to fix timezone issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants