L3 - Default Context:
- different users in different timezones use the tasklist collaboratively
Problem Description
Example 1:
- Given User 1 in Timezone 1 and User 2 in Timezone 2
- if User 1 sets the Duedate for a task
- then, in the default configuration, it shows up wrong in the when User 2 looks at the task
- expected: the timezone offset is taken into account when sending duedate on backend and showing the duedate to User 2
Example 2:
- Given User 1 in Timezone 1 and User 2 in Timezone 2
- if User 1 creates a task
- then a wrong value for "created X minutes ago" is shown
- expected: "created X minutes ago does not include a timezone offset
Example 3:
- Given User 1 in Timezone 1 and Process Engine in Timezone 2
- if process engine creates a task or sets the duedate for a task
- expected: offset between process engine timezone and user timezone is taken into account when displaying create time
AT:
- Using tasklist in different timezones works
Implementation Notes:
- Rest API inside Webapp returns all dates in UTC
- Webapp converts dates into user's local time before displaying them
- Webapp converts all dates to UTC before sending them to the server
Problems:
- backwards compatibility of Rest API
- special considerations for dates in task forms?