Fix

Saving a project no longer resets a setting you never touched

The project edit form could show a stored setting as its default and then save that default back. It now waits until it has loaded everything before it will let you save.

The project edit form loads its fields from several places at once — the headline details, the billing and invoicing fields, and the budget each arrive separately. If you saved while one of those was still outstanding, the form sent what it was showing, and what it was showing was a blank.

The catch is that a blank is a legitimate answer. An unticked checkbox means "no" and an empty number means "none", so there was nothing to warn you about and nothing in the saved project to suggest anything had gone missing. The case that brought it to light was Push linked entries to Jira as worklogs, which is on by default for new projects: the box rendered unticked, there was no reason to tick something that should already have been on, and saving turned it off.

The form now waits until every field can show what is actually stored before it will render, and says so plainly if a project cannot be loaded at all rather than offering you a form full of defaults.

Worth a look if you use the Jira integration. If worklog sync is off on a project you expected it to be on for, it is on the project's edit page under the Jira heading — tick it and save. Nothing else about the project was affected, and no time entries were changed.

← Everything that has changed

The hours, the invoices, and what they earned

Free for unlimited people. One paid plan, $10 per member per month, when you want HR, scheduling, timesheet approvals, scheduled backups, email from your own domain and scheduled reports.

Start free