What problem does this address?
The system currently relies on a default or implicit timezone, which can lead to inconsistencies in date/time handling across features such as scheduling, logs, timestamps, and user-facing displays. This becomes problematic for users operating in different regions or when the server timezone differs from the intended application context.
Proposed solution
Introduce a configurable timezone setting that can be defined at the application (and/or user) level. This setting should be used consistently across all date and time operations, including storage, display, and scheduling logic. The default behavior should remain unchanged unless a timezone is explicitly configured.
Additional context
No response
What problem does this address?
The system currently relies on a default or implicit timezone, which can lead to inconsistencies in date/time handling across features such as scheduling, logs, timestamps, and user-facing displays. This becomes problematic for users operating in different regions or when the server timezone differs from the intended application context.
Proposed solution
Introduce a configurable timezone setting that can be defined at the application (and/or user) level. This setting should be used consistently across all date and time operations, including storage, display, and scheduling logic. The default behavior should remain unchanged unless a timezone is explicitly configured.
Additional context
No response