[Vacay] Configurable Vacation Year: Fiscal Year & Anniversary Calendar Support

[ClaymoreTech4]

The Vacay addon currently assumes a standard January 1 – December 31 calendar year for vacation accrual and reset. Many organizations don't operate on this cycle.

For example: Fiscal year calendars — e.g., July 1 to June 30, or October 1 to September 30 Anniversary calendars — vacation days reset on the employee's hire date anniversary each year (e.g., if hired March 15, the vacation year runs March 15 → March 14)

Without support for these, the carry-over tracking, day counts, and calendar view all show incorrect information for users whose companies use a non-standard year.

Describe the solution you'd like Add a Vacation Year Type setting to the Vacay addon, configurable per user (or globally by admin). The setting should support three modes:

Calendar Year (current default) — January 1 to December 31 Custom Fiscal Year — Admin/user sets a start month and day (e.g., 07-01 for July 1). The year runs 12 months from that date. Anniversary Year — User sets their hire date. The vacation year resets on the anniversary of that date each year.

UI changes needed:

In Vacay settings, add a "Vacation Year Type" selector (Calendar / Fiscal / Anniversary) When Fiscal is selected: show a date picker for the year start (month + day only) When Anniversary is selected: show a date picker for the hire date (full date, used to compute the rolling anniversary window) The calendar view should visually reflect the active year window — e.g., if the year runs July 1 → June 30, the calendar should highlight that range and show carry-over at the correct boundary

Logic changes needed:

All day-count calculations, carry-over logic, and "days remaining" tallies should be computed relative to the configured year window, not hardcoded Jan–Dec The year window should auto-advance — e.g., after July 1 passes, the system moves to the new fiscal year automatically For Anniversary calendars, the year window should be computed dynamically from the stored hire date each time

Why this matters This is extremely common in real-world HR scenarios:

Government and education employers often use fiscal years Many private employers give vacation based on tenure, resetting on the hire anniversary Without this, Vacay carry-over tracking is actively misleading for a large portion of potential users

[Flori991]

Same in the UK, where it actually goes from April till March, so we would ideally need configurable dates for start end, not some pre-configured ones if possible.

[gritting]

This would definitely be appreciated. The existing implementation with fixed Jan-Dec cycle is not usable for me at all for the reasons stated in the OP. The described solution with per-user calendar modes would be perfect for me.

[mauriceboe]

@ClaymoreTech4 @Flori991 @gritting
Coming in 4.0.0! <3