Milestones with their own settings
August was a short month of 10 commits. The most useful change was giving each time-off policy milestone its own options field. In June we moved policy settings into a flexible options store; this month the same idea reached the milestones, so each step in a policy can carry its own rules without new columns being added every time a rule changes. For employers this means a policy can, for example, treat someone in their first year differently from someone in their fifth, and the rules can be extended later without a disruptive change to stored data.
We also updated the settings module and made two small sorting changes.
Remuneration and employee updates
Mid-month we returned to the remuneration and employee modules, tightening their checks and updating the sample data we use to test them. These are not headline features, but they kept the pay side of the codebase consistent with the time-off work, and the refreshed sample data made it easier to check that both behaved as expected together.
After August, activity on this codebase slowed for most of a year. The next substantial burst of work came in November 2025, when we started rebuilding on the shared core used by Mintage Payroll.
This article was written from Mintage TimeKeeper’s commit history for August 2024. See Mintage TimeKeeper today