Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Account for user journey when calculating days booked per week #633

Draft
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

dmtrek14
Copy link
Collaborator

Currently, the Vacation Management page shows Days Booked per Week and includes partial leaves (days where the number of of hours is less than a user journey), but doesn't account for a user booking more vacation hours than their workday hours (journey). This is normally not something to worry about too much since most users will probably use the Vacation Management page to book vacation and that interface takes care of handling the right amount of hours based on journey. However, if the user manually books vacation time via the Tasks page, there could be some days on which the user has more hours booked for vacation than they should. When this happens (more hours booked than should be allowed for a day), the Days Booked per Week does not take the user journey into account and will simply show 1 day booked on a week when it should perhaps show 1.25 days.

This PR adds accounting for user journey in the calculation of Days Booked per Week and also adds highlighting to days on which a user has booked more vacation hours than their journey.

@dmtrek14 dmtrek14 marked this pull request as ready for review May 30, 2023 20:09
@dmtrek14 dmtrek14 requested a review from anarute May 30, 2023 20:10
@dmtrek14 dmtrek14 changed the title Account for user journey when calculating days in summary Account for user journey when calculating days booked per week Jun 1, 2023
@dmtrek14 dmtrek14 marked this pull request as draft June 20, 2023 14:54
@dmtrek14
Copy link
Collaborator Author

Putting this one on old - there's some unforeseen complexity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant