🔀 Versioning. Version History

Versioning — a key feature missing in Upbase

Versioning is missing — this is one of the most important features that has not been implemented.

In practice, it has happened many times that data simply disappeared or was deleted.

Examples of issues

• Partial or complete loss of content when a document/change was not saved correctly.

• Accidental deletion of an item by a user.

• No ability to restore previous versions after an incorrect edit.

Where versioning is needed

• Documents — tracking changes, comparing versions, restoring previous versions.

• Tasks — change history of descriptions, statuses, due dates, and comments.

• Other collaborative elements where changes are frequent and critical.

Expected features (minimum)

• Automatic periodic saves (autosave) and a final save on closing.

• Ability to view change history (list of versions).

• Restore a selected version with one click.

• Information on who made the change and when (author + timestamp).

• Optional version comparison to show differences.

Benefits

• Minimizes the risk of data loss.

• Allows quick rollback of erroneous changes.

• Improves control over team collaboration.

• Increases safety and user confidence.

Priority

• Versioning should have high priority — not only for documents, but also for tasks and other critical elements of Upbase.