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
Describe the current limitation
Current estimated time to leave is misleading if you have an enforced minimum break time.
Describe the proposed feature or enhancement
Take into account break time for the estimated time to leave. Add an option to toggle this for users that prefer the previous behavior.
The text was updated successfully, but these errors were encountered:
#1083 had a go at a solution, but the ultimate one needs to account for more things. Today we have two scenarios on the app:
No enforced break time
Enforced break time
On both scenarios, the "Leave by" is properly updated as soon as the break has been finished/computed, which for the first is when the user punches back and for the second is as soon as they punch out to begin the break.
We cannot do any better for scenario 1 in terms of estimating the "Leave by", since we cannot now the break time, but for the second scenario we can. To be fully functional, it does bring some more complex questions:
How many enforced breaks does the user have? We currently consider only one (which is by default how many breaks are there on the screen). It can prefill if the user has previously added more empty entries.
Does the user have a number of enforced breaks and non-enforced?
That brings the question of maybe bringing in an additional preference of "number of enforced breaks". This would make it easier to automatically input the breaks for case option 1 and also to know when to stop inputting it if the scenario 2 happens.
Describe the current limitation
Current estimated time to leave is misleading if you have an enforced minimum break time.
Describe the proposed feature or enhancement
Take into account break time for the estimated time to leave. Add an option to toggle this for users that prefer the previous behavior.
The text was updated successfully, but these errors were encountered: