[Bug / Feature] Data Loss if 2 Users work on the same Task #1812
Labels
No Label
dependencies
duplicate
help wanted
invalid
kind/bug
kind/feature
needs reproduction
question
security
wontfix
No Milestone
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: vikunja/vikunja#1812
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
We just yesterday noticed, that a friend of mine had a Task open and saved it, after I added some content to it. We then noticed, that his saving of the old version has overwritten my progress.
Is there some Locking system planned, that blocks other users from editing content of a field/task? (Commenting should still be fine right?)
An alternative would also be just replacing the pencil with a lock icon and showing a tooltip.
Ideally you would be able to work simultaniously on the same task with auto-updates and such (And that's actually something I'd like to build at some point in the future).
I think locking or at least a notification, something like "this task is currently being edited by another user", would be a good addition.
This is a bit more complicated as it requires a bit more changes on the api-side.
More discussion in vikunja/frontend#765
OrangePony referenced this issue from vikunja/frontend2021-09-21 20:33:26 +00:00
That sounds nice! :)