When starting tasks and orders for a later point in time the time zone should be specified

Current Situation

• Whe starting tasks or orders manually then the time scheduling doesn't have a time zone so when I select midnight I'm not confident that I will get London midnight or UTC midnight and the updated next runtime doesn't seem to update in the daily plan or on the dashboard.

Desired Behavior

• Users should be able to indicate a time zone when specifying a manual start for a task or order for a later point in time.
  • Specifying e.g. "15:30" currently is interpreted from the Master to happen in the Master's time zone, however, this could be different from the user's time zone.
• Therefore the list of time zones should be displayed with the time zone of the user profile being used by default. Users should be able to select a different time zone for the individual start of a task or order.

Implementation

• Clarification required: one option includes that the JOC Cockpit will add the time zone to the timestamp of the respective REST API call. A second option includes to specify the time zone from a separate property. It's up to the development team to decide about this.

Maintainer Notes

• Please consider the linked SourceForge thread.