kimai / Paid-plugins

Support for paid Kimai plugins: Discussions and feature requests
https://www.kimai.org/store/
11 stars 1 forks source link

Feature Request: Remove limit of absence days #181

Open pkoevesdi opened 3 months ago

pkoevesdi commented 3 months ago

One can only set maximum of 20 holidays, 15 days of sickness at a time. Don't know, why this limit exists. I don't see a reason for any limit at all (from the user's perspective), but at least it should be made to be configured or switched off by the admin. In case, there's a good reason to keep any limit, please raise it. I suggest for holidays 40 days. That would cover for instance 30 days we have in our company plus holidays carried forward from last year. Still not covered would be things like Elternzeit and other long-term absences, so first prio I'd say: switch off the limits at all.

Thank You!

kevinpapst commented 3 months ago

There is only a limit for vacations to prevent accidentally creating invalid long periods. 20 days in a row means 4 weeks. This is 2/3 of the yearly holidays (in many countries it is more than the entirely yearly available days). Is that really a common case in your company?

Stuff like "Parental leave" use a different flow:

Bildschirmfoto 2024-07-29 um 10 24 17
pkoevesdi commented 3 months ago

There is only a limit for vacations to prevent accidentally creating invalid long periods. 20 days in a row means 4 weeks. This is 2/3 of the yearly holidays (in many countries it is more than the entirely yearly available days). Is that really a common case in your company?

Yes, it is. I wanted to take a big summer vacation, 23 days out of 37 I have at the moment, and already failed. You could warn the user above that limit, if You want to hinder him from making mistakes, but not disallow him to do what he really wants, without workaround. At least I'll keep up my suggestion to raise that limit to 30...40.

Thank for pointing to parental leave.

pkoevesdi commented 3 months ago

Just want to add: If a user makes a mistake, he can easily correct it, and remove the incorrect entries. So why bother with some unneccesary safety belt at this point, especially by disempowering the administrator? It's his or the user's responsibility to make correct entries, not the developer's. :-)