You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I don't have a precise feature request, it's rather a call for opinions about a functionality that is missing IMHO.
It would be great if I could add the info that on a particular day I was x% off (e.g. half day 50%, or full day off / vacation)
The call for opinions: How to display such that days?
On the one hand, I would like to see how much overtime I have made this week, month, year etc. I think that in this case it would be good if there would be an option to show a day on that I was x% off with x% of a regular working day (say if I was 50% off, i.e., leaving after lunch, it would be like 4hours + the time I worked).
On the other hand, I sometimes would just like to know how much time I actually worked (such that there should be a way to turn on/off this way of counting)
What is your opinion on that matter?
The text was updated successfully, but these errors were encountered:
I need to think about this, but my initial thoughts are that it will be quite difficult to cover all different use cases, different calendar systems, and different public holidays around the world. Probably something I'm not ready to get into.
The original idea of this app was to act like a simple working hours log for yourself. Also, the implementation is simple and quite bad tbh, so adding new complex features would almost need a rewrite of the database logic.
Thanks for your reply!
I am not sure whether this would require new complex features. What I actually though of is like an extra button that says: "Book today as vacation day" and then it takes from my default work week 1/5 of the hours and marks that day as vacation in the database.
I don't have a precise feature request, it's rather a call for opinions about a functionality that is missing IMHO.
What is your opinion on that matter?
The text was updated successfully, but these errors were encountered: