Fossil SCM
Suggestion: label for timestamp in the eventedit form
05f4bbc266e2209…
· opened 12 years, 11 months ago
- Type
- Feature_Request
- Priority
- —
- Severity
- Important
- Resolution
- Fixed
- Subsystem
- —
- Created
- April 19, 2013 10:27 a.m.
By default, Fossil uses UTC for the timestamps of commits, tickets, events, etc. This is fine when the user is not allowed to specify the timestamp manually. In cases where the user can edit the timestamp manually (as happens with the HTML event edit form), the user can quite easily forget that he/she might be inserting a timestamp on his/her localtime instead of the server time (UTC).
The suggestion is therefore to simply include a "UTC" label right next to the "t" textfield in the Edit Event form.
Comments (2)
By default, Fossil uses UTC for the timestamps of commits, tickets, events, etc. This is fine when the user is not allowed to specify the timestamp manually. In cases where the user can edit the timestamp manually (as happens with the HTML event edit form), the user can quite easily forget that he/she might be inserting a timestamp on his/her localtime instead of the server time (UTC).
The suggestion is therefore to simply include a "UTC" label right next to the "t" textfield in the Edit Event form.
Fixed in [635598ed936c6].