Content
View differences
Updated by Parimal Satyal about 1 year ago
**Context**
This feature should be evaluated together with a related feature, which already sets the default time to 9h with quick-set options: ##60357
**Acceptance criteria**
* When created a new reminder:
* The Time field is pre-set to 9:00 AM
* _\[open\] PS: Alternatively, we can allow the Time field to be empty and just internally set it to 9h, but I htink this is more intuitive_
**Technical notes**
* The time has to always be set in the user's account time zone
* \[open\] If the user changes her time zone after setting a Reminder; the reminder time is moved such that it is the same time in the new time zone (eg. If a reminder was set at 10h whilst on UTC and the user changes their time zone to CEST, they will still get the reminder at 10h CEST).
**Permissions and visibility considerations**
* None
**Translation considerations**
* \-
**Out of scope**
* <br>
This feature should be evaluated together with a related feature, which already sets the default time to 9h with quick-set options: ##60357
**Acceptance criteria**
* When created a new reminder:
* The Time field is pre-set to 9:00 AM
* _\[open\] PS: Alternatively, we can allow the Time field to be empty and just internally set it to 9h, but I htink this is more intuitive_
**Technical notes**
* The time has to always be set in the user's account time zone
* \[open\] If the user changes her time zone after setting a Reminder; the reminder time is moved such that it is the same time in the new time zone (eg. If a reminder was set at 10h whilst on UTC and the user changes their time zone to CEST, they will still get the reminder at 10h CEST).
**Permissions and visibility considerations**
* None
**Translation considerations**
* \-
**Out of scope**
* <br>