I often have the case of working past midnight. Then, I can no longer easily see my total worktime of the day (as in "since last sleep", not as in "0:00 – 24:00") since the "Today" column is reset at midnight.
Other timetrackers (for example Hamster) solved this issue by allowing users to configure what is considered as "today"). But that seems more like a hack and would cause confusion in the rest of the software, such as: certain hours would belong to a different month when locally configuring "midnight" differently, and doing that in reports would formally not be correct.
Instead, simply adding a column "Yesterday" to the project tree seems a clean solution.
That would be a lot of columns then, but they could be hideable (will propose that in another issue). For example, in exchange I would not display the "This week" and "This month" column usually.
I often have the case of working past midnight. Then, I can no longer easily see my total worktime of the day (as in "since last sleep", not as in "0:00 – 24:00") since the "Today" column is reset at midnight.
Other timetrackers (for example Hamster) solved this issue by allowing users to configure what is considered as "today"). But that seems more like a hack and would cause confusion in the rest of the software, such as: certain hours would belong to a different month when locally configuring "midnight" differently, and doing that in reports would formally not be correct.
Instead, simply adding a column "Yesterday" to the project tree seems a clean solution.
That would be a lot of columns then, but they could be hideable (will propose that in another issue). For example, in exchange I would not display the "This week" and "This month" column usually.