Setting Up Half-Day and Partial Leave Policies in Jira
The same specific complaint, twice, in two different apps
This is a rare case where the evidence for a design decision comes from two entirely separate, real, dated reviews of two different competing apps, both describing the identical underlying frustration:
- A 2-star review of UpRaise Employee Garrison: rounding leave to the nearest 0.5 day “makes zero sense” for partial-day requests.
- A 2020-10-07 review of Vacation Manager for Jira: an explicit request that “christmas eve and silvester are ‘half work days’” get automatic half-day deduction, rather than being forced into a whole-day model.
Two products, two years apart, two different specific complaints — but the same underlying gap: rigid whole-day (or crudely rounded) accrual doesn’t match how organizations actually grant partial-day leave, especially around specific recurring dates like a half-working-day before a holiday.
How OutSync’s half-day handling actually works
Step 1: Enable half-day increments in the accrual policy. From the admin’s Org settings tab, “Allow half-day increments” is an explicit toggle alongside days-per-year and carryover — off by default in the sense that it’s a deliberate choice, not a forced behavior, for organizations where leave policy genuinely deals in half-days.
Step 2: An employee checks “Half day” when submitting a request. The request form’s Half day checkbox is only meaningful — and only valid — when the start date and end date are the same calendar day. This is enforced by validation, not left as a toggle someone could accidentally combine with a multi-day date range and get an ambiguous result.
Step 3: The deduction math handles the exact edge case both competitor reviews were asking about. A half-day request deducts exactly 0.5 from the balance — unless that single date falls on a configured public holiday for the team, in which case it deducts zero. This is the precise scenario Vacation Manager’s 2020 review named directly: a half-working-day before a holiday shouldn’t cost 0.5 of an already-excluded day. OutSync’s accrual math checks the holiday-exclusion set for that exact date before applying the half-day deduction, so a half-day request landing on, say, a locally observed Christmas Eve deducts nothing rather than double-charging a day that was never really taken out of the employee’s balance.
Why this needed to be precise, not approximate
UpRaise’s review complaint — rounding to the nearest 0.5 “makes zero sense” — points at a common, blunter approach: treat every partial-day request as a flat 0.5, regardless of context. That’s simpler to build, and it’s exactly what breaks the moment a half-day request happens to fall on a day that’s already fully or partially excluded from the balance for another reason (a public holiday, most concretely). Getting this right required accrual math that checks the holiday-exclusion state for the specific date in question before deciding how much to deduct — not a flat rule applied the same way regardless of context.
What this doesn’t cover
Half-day increments are a leave-request-level setting, not a per-employee schedule configuration — OutSync doesn’t currently model a person’s actual part-time working pattern (e.g., someone who works mornings only). It solves the specific, reviewed gap of “a leave request can legitimately be half a day, and that should deduct correctly against the balance,” not a full part-time-scheduling system.
Related reading
Frequently asked questions
Can a half-day leave request span more than one day?
No, by design — a half-day request must start and end on the same calendar day. This is enforced by validation, not left as an easy-to-misuse toggle a multi-day request could accidentally combine with.
What happens if a half-day request falls on a public holiday?
It deducts zero from the balance, not 0.5. If a team has a public holiday region configured and the half-day's date falls on one of that region's holidays, the day is already excluded from the balance entirely — charging half a day on top of an already-excluded day would double-count something that was never really taken from the employee's balance.
Does every organization need to allow half-day increments?
No — it's a configurable accrual-policy setting, off by default in the sense that it's an explicit choice, not a forced behavior. Organizations whose leave policy only ever deals in whole days can leave it as-is; the setting exists for organizations where half-days are a normal, real part of how leave gets requested.