Maintenance start/end time input incorrectly uses system timezone

[lougedada]

⚠️ Please verify that this bug has NOT been raised before.

• I checked and didn't find similar issue

🛡️ Security Policy

• I agree to have read this project Security Policy

Description

I set the Chinese time, but after exiting, the time displayed was 1 hour later than the set time, but the actual execution time was correct.

👟 Reproduction steps

Select the time zone as Shanghai and set up planned maintenance

👀 Expected behavior

Time display leading to status page errors

😓 Actual Behavior

Status page error time display

🐻 Uptime-Kuma Version

1.23.6

💻 Operating System and Arch

Ubuntu 22.04.3 LTS

🌐 Browser

edge

🐋 Docker Version

Docker version 24.0.5, build 24.0.5-0ubuntu1~22.04.1

🟩 NodeJS Version

No response

📝 Relevant log output

No response

[CommanderStorm]

Could you try restarting your instance as noted in #3626

[lougedada]

Could you try restarting your instance as noted in #3626

I am using this model. It is okay if I try according to the model in the article you mentioned, but the single time model is wrong.

[imlonghao]

I'm able to reproduce this issue. IT IS RELATED TO YOUR BROWSER/SYSTEM TIMEZONE.

Let's say we have a planned maintenance on 2023-11-30 10:00-11:00 (UTC+8), aka 2023-11-30 11:00-12:00 (UTC+9)

How to reproduce:

1. Change your system timezone to Asia/Tokyo (UTC+9)
2. Go to https://demo.uptime.kuma.pet/ and create a demo instance
3. Create a New Monitor, whatever target is ok
4. Go to Schedule Maintenance and create a maintenance as the screenshot
   
5. Now you can see from the list, the maintenance is shown as 2023-11-30 09:00 - 2023-11-30 10:00 UTC+08:00 Asia/Shanghai, which is an hour earlier than expected.
   

Related to this code block:

uptime-kuma/src/components/MaintenanceTime.vue

Lines 30 to 37 in 80efe9b

	computed: {
	startDateTime() {
	return dayjs(this.maintenance.timeslotList[0].startDate).tz(this.maintenance.timezone).format(SQL_DATETIME_FORMAT_WITHOUT_SECOND);
	},
	endDateTime() {
	return dayjs(this.maintenance.timeslotList[0].endDate).tz(this.maintenance.timezone).format(SQL_DATETIME_FORMAT_WITHOUT_SECOND);
	}
	},

[jaybhanushali3166]

Hi @chakflying / @CommanderStorm,
I'd be interested to work on this bug. May you please assign it to me?

[chakflying]

I don't think this issue is complicated enough to require assignment, and we don't assign issues here in general. If you have a solution you can open a pull request following the guidelines.