2026.1.4 — 21 October 2026
Defect
- Value items created with the quick create box can now have spaces in their name.
Debt
- Strategy, mission, vision and values are maintained through one code path per operation, so future changes to them stay consistent across the product.
2026.1.3 — 19 October 2026
Feature
- The versions list is ordered by release date, newest first, so the current release sits at the top
Defect
- The footer link in the version selector opens again, instead of only looking like a link
Debt
- A contact’s details are now resolved the same way on a client and on its projects, so the two can no longer disagree
2026.1.2 — 19 October 2026
Feature
- Organizations are emailed before their webhook secrets expire, with a reminder a week ahead and a final notice the day before
Defect
- Pushes to a connected repository are no longer dropped silently — the referenced value item now shows the commit
Debt
- Server logs no longer repeat the timestamp on every line
- Access permissions are now checked in one place, so what each role may see or change stays consistent
- Frontend changes are checked and built faster, so fixes and improvements reach customers sooner
2026.1.1 — 8 October 2026
Defect
- Platform administrators can now use the administrator-gated areas of the application
- Timestamps on reference data displayed up to two hours early and now show the correct time
- Automated maintenance for an organization no longer stops early in rare cases
Risk
- Configuring the worklog approval workflow is now limited to organization and platform administrators
- A release now refuses to start against a database that carries migrations it does not know
2026.1.0 — 5 October 2026
Feature
- Time spent on work is recorded in worklogs, against the item it belongs to and the person who did it
- Timesheets collect a person’s worklogs for a period and carry a status from draft through review to approval
- A timesheet can be submitted, returned with a reason, and approved by whoever is accountable for that person’s time
- Working-hours and holiday schemes are kept per person, and a timesheet is measured against that person’s own scheme
- Client projects can be priced with rates and budgets, and an overview shows how much has been used against them
- People settings gather the catalogs of job positions, roles and rates onto pages of their own, with paging for the long ones
- User groups are managed at the organization account, so access can be granted to a set of people at once
- Notifications reach a person by email when work arrives with them, through the channels they have chosen
- The public API exposes people, organizational units, value units and key results, so an integration can read and write them under an API key
- The timezone a person selects is used wherever a time is shown to them
- A value item records how long it stayed in each status
- Time management and settings meet the keyboard and screen-reader requirements, including their save flows
Defect
- Timesheet export covers the scope that was chosen, rather than only the person who ran it
Risk
- The build pipeline scans for credentials that were committed by accident
Debt
- The path that updates a person was rewritten so that its rules live in one place
- Every form was moved onto a single pattern, so form behaviour is the same across the product
- The interface was upgraded to the current Angular release line
- The frontend test runner was replaced, which shortens the loop between a change and knowing that it works
- Deleted records are handled the same way across the core entities, so a deletion that should be recoverable is recoverable
- Logging was completed across the backend, so a problem can be traced from the log alone
- The automated suite grew across the API, the interface and the architecture rules, so a change that breaks a boundary fails before it ships
- The subscription status is displayed the same way on every screen that shows it
- Release notes are now compiled from each change as it is merged, instead of being reconstructed by hand at release time
- Frontend changes are now described for customers as they are merged, instead of being written up by hand at release time
- Frontend release candidates are no longer held up by an out-of-memory test run