Sprint history — Leave

What shipped

Leave requests and their approval, plus the rule that keeps leave out of the roster.

• Leave management + LeaveConflictRule (MIQ-030) — LeaveRequest, the request flow, and the LEAVE_CONFLICT allocation rule that reads real leave data so on-leave workers aren't allocated.
• Multi-step leave approval (MIQ-030a) — the 2-step Manager → HR_Admin approval chain, server-side overlap checks, and a RowVersion fix.

Key decisions

• No LeaveType taxonomy — there is no Annual/Sick/Vacation classification; a request has no type field (sheet 11).
• Cancel sets status, not soft-delete — cancelling sets Status = Cancelled, not IsDeleted.
• The LEAVE_CONFLICT hard rule reads real leave data — leave actually blocks allocation (Phase-0: leave is LIVE, not planned).

Build status

Available — LeaveRequest + LeaveApprovalStep, the 2-step chain, and the conflict rule all ship. See Submit & track leave, Approve leave, and the Leave API.

Related

• Fact sheet 11 (leave management); reports MIQ-030/030a.