Thanks yeah, that would be the way to go, in most cases. Unfortunately, most employers use in their business the official local time of their country instead of UTC. And when there is a due date at 10, a software saying it is at 11 (because it counts only the seconds within working time declared by the user, mapping every segment of checked expenditure to them, so the time-related criteria in urgency calculation is realistic), well, it can turn out as a annoyance for the user to have to calculate around it when entering tasks and planning their time model. That is why I chose local time. I the developer may have to solve these issues, not him.
In reply to Re^2: Is there an official DST border day detection module?
by flowdy
in thread Is there an official DST border day detection module?
by flowdy
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |