We auto-save patient form in many cases, e.g. every time before opening pedigree editor, or every time before pushing. This creates unnecessary blank history states for the patient document, and slows the UI interaction. Since implemented "unsaved change" detection, we should now use similar logic to decide if we need to auto-save patient data or not in all those cases as well
: There's some work in progress that you can already test on https://dev.phenotips.org.
Here's the expected behavior:
periodic autosave (which is called every 10s on dev.phenotips.org) only saves the patient/family form if there are unsaved changes. I.e.. you can keep it open for hours and without changing anything it shouldn't create new versions, but while you are entering data in the form you should see the little green "Saved" notification pop at the bottom of the screen every 10 seconds
when you open the pedigree editor, you should see "Saved" pop up only if there are unsaved changes (now in PhenoTips it's every time you open the pedigree from the patient or family form)
similarly, when you click on Export (PDF, JSON, XAR) or Push to ... from the menu in edit mode, you should only see "Saved" only if there are unsaved changes (now in PhenoTips it's every time you if you're in edit mode).
Also, to make sure that there are no regressions, please test that when navigating away from a patient/family form with unsaved changes the user is warned and prompted if they really want to leave the page.