Recruitment and support tickets begin

A recruitment module

July was a lighter month, with 11 commits. The main addition was a first version of a recruitment module, plugged into the same modular core as the HR and remuneration work from earlier in the year. It arrived in two passes on consecutive days: the module itself first, then a round of changes to the endpoints that other parts of the system call.

Over the following days we refined its endpoints. One small but practical change made a phone number required and an email address optional.

A place for support tickets

At the end of the month we added a ticket module, the start of a way to log and follow support requests inside the product, and connected it to the settings module so it could be configured like everything else. We also began returning a short, readable slug in responses so that records can be referred to by something friendlier than an internal number.

The remaining commits were module updates and merges that kept the pieces in step with each other.

Where this fits

At this stage the codebase was still a general HR base rather than a time and attendance product. When TimeKeeper was restarted in 2026, the module list was cut back to what a time and attendance product needs; the modular design made it easy to try ideas here and leave behind what did not belong.