V15 - Scheduled publish dates wrong when client and server are in different timezones

[kraftvaerk-chth]

Which Umbraco version are you using? (Please write the exact version, example: 10.1.0)

15.0.0

Bug summary

When scheduling a publish of a document, the publish date is wrong if the timezones of the client and server are different

Specifics

No response

Steps to reproduce

Create a setup of Umbraco where the server is running in one timezone (fx UTC), and your own machine is running in another (fx UTC+1)

Schedule a document for publishing in 1 minute from now
The document will not be published in 1 minute, instead it will be publised in 1 hour (depending on the timezone difference between client and server)

Expected result / actual result

Expected result: The time set for scheduled publish should be in the same timezone as the client who scheduled the publish
For example if I'm in UTC+1 and schedule a publish for 14:30, the document should be published 14:30+1, regardless of the server's timezone

Actual result: The difference between the client and server timezone makes the scheduled publish of a document unpredictable to the editor - they need to know the current timezone difference between themselves and the server to be able to calculate the correct publish time

---

This item has been added to our backlog AB#47430

[github-actions]

Hi there @kraftvaerk-chth!

Firstly, a big thank you for raising this issue. Every piece of feedback we receive helps us to make Umbraco better.

We really appreciate your patience while we wait for our team to have a look at this but we wanted to let you know that we see this and share with you the plan for what comes next.

• We'll assess whether this issue relates to something that has already been fixed in a later version of the release that it has been raised for.
• If it's a bug, is it related to a release that we are actively supporting or is it related to a release that's in the end-of-life or security-only phase?
• We'll replicate the issue to ensure that the problem is as described.
• We'll decide whether the behavior is an issue or if the behavior is intended.

We wish we could work with everyone directly and assess your issue immediately but we're in the fortunate position of having lots of contributions to work with and only a few humans who are able to do it. We are making progress though and in the meantime, we will keep you in the loop and let you know when we have any questions.

Thanks, from your friendly Umbraco GitHub bot 🤖 🙂

[NguyenThuyLan]

I was able to reproduce on Umbraco Cloud (v14 and v15) but not on v13. Thank you, @kraftvaerk-chth, for reporting this issue.

[leekelleher]

Fixed in #17868 for Umbraco 15.3.0.