Timezone selection in scheduled trigger does not show current UTC offset

[octopus-hideaki]

Severity

Sev 3 - Non blocking

Version

Earliest tried 2024.2

Latest Version

I could reproduce the problem in the latest build

What happened?

When creating scheduled deployment or runbook triggers, users can select a time zone and the local time for the trigger.

The timezone dropdown displays the UTC offset and the corresponding timezone name.

These offsets are based on the base time zone offset and do not reflect the current time zone's adjustments. For example, during daylight saving time, the UTC offset is for the standard time instead of daylight saving time.

Note: The created deployment triggers take daylight saving time into consideration.

Reproduction

1. Create a scheduled deployment/runbook trigger
2. Select a time zone that is currently observing daylight savings
3. Observe that the time zone is showing the UTC offset for the standard time
4. Wait for the deployment/runbook to be triggered
5. Observe that the deployment/runbook run occurred at daylight saving time

More Information

The trigger:

The deployment:

Workaround

Ignore the UTC offset shown on the dropdown.

[michelle-luana]

The Octopus engineering team has reviewed this issue.
After careful consideration, we’ve classed this low priority. This means we won’t work on it in the near future.
We prioritize issues based on the number of people affected, the impact type, and available workarounds.
If you’ve encountered this issue and haven’t informed our support team, please email support@octopus.com. Knowing how many people this issue affects helps us determine its priority.