j
/
punchclock
1
0
Fork 0
Code Issues 3 Releases 1 Activity

handle timezones or UTC #3

New Issue
Open
opened 2023-07-20 07:41:01 +02:00 by j · 0 comments
j commented 2023-07-20 07:41:01 +02:00
Owner
Copy Link

currently all dates are being kept and calculated in UTC.

it might make sense to be able to do at least the calculations in the local timezone or a timezone of the users choosing.

especially when tracked intervals cross a UTC daychange the summaries become unintuitive.

currently all dates are being kept and calculated in UTC. it might make sense to be able to do at least the calculations in the local timezone or a timezone of the users choosing. especially when tracked intervals cross a UTC daychange the summaries become unintuitive.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
main
0.0.1
Labels
Clear labels
No items
No Label
Milestone
Clear milestone
No items
No Milestone
Assignees
Clear assignees
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Reference: j/punchclock#3
No description provided.
Delete Branch "%!s(<nil>)"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?