In workpatterns_classify(), the documentation currently refers to breaks with respect to the recurring hourly slots where an employee has not sent out an instant messages or emails (depending on user setting). This is likely to give rise to confusion because breaks can be legitimately non-recurring, and may therefore being interpreted as an overly strict definition.
Instead, the wording for breaks can be replaced with recurring disconnection time, which is a more accurate representation of what the metric measures. This should just be a change to the documentation without any impact to the code.
In
workpatterns_classify(), the documentation currently refers to breaks with respect to the recurring hourly slots where an employee has not sent out an instant messages or emails (depending on user setting). This is likely to give rise to confusion because breaks can be legitimately non-recurring, and may therefore being interpreted as an overly strict definition.Instead, the wording for breaks can be replaced with recurring disconnection time, which is a more accurate representation of what the metric measures. This should just be a change to the documentation without any impact to the code.