Finish timezone support
Registered by
Sergei Golubchik
There're undoubtly bugs in the timezone support. For example: a case when an item is split between two days (2-hr appt that starts at 23:00 in some tz) is not handled correctly; Item::first, next, range, set_start, set_finish, delete_occurence are probably broken when timezone is set.
Blueprint information
- Status:
- Not started
- Approver:
- None
- Priority:
- Medium
- Drafter:
- None
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- New
- Series goal:
- None
- Implementation:
- Unknown
- Milestone target:
- None
- Started by
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
(?)