vikunja/vikunja
5
48
Fork 85
Code Issues 150 Pull Requests 38 Packages Releases 37 Activity

[Bug / Feature] Data Loss if 2 Users work on the same Task #1812

New Issue
Closed
opened 2021-07-16 07:17:56 +00:00 by Gensokian · 3 comments
Gensokian commented 2021-07-16 07:17:56 +00:00
Copy Link

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?)
image

An alternative would also be just replacing the pencil with a lock icon and showing a tooltip.

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?) ![image](/attachments/923b7813-2a02-422f-8256-89c16e7e7532) An alternative would also be just replacing the pencil with a lock icon and showing a tooltip.
image.png
192 KiB
konrad added the
kind/bug
kind/feature
 labels 2021-07-19 09:24:39 +00:00
konrad commented 2021-07-19 09:27:39 +00:00
Owner
Copy Link

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.

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.
konrad commented 2021-09-21 19:53:14 +00:00
Owner
Copy Link

More discussion in vikunja/frontend#765

More discussion in https://kolaente.dev/vikunja/frontend/issues/765
dpschen commented 2021-09-22 11:47:17 +00:00
Member
Copy Link

at least a notification, something like "this task is currently being edited by another user", would be a good addition.

That sounds nice! :)

> at least a notification, something like "this task is currently being edited by another user", would be a good addition. That sounds nice! :)
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
dependencies
duplicate
This issue or pull request already exists
help wanted
Need some help
invalid
Something is wrong
kind/bug
Something is not working
kind/feature
New feature
needs reproduction
question
More information is needed
security
wontfix
This won't be fixed
No Label
Milestone
No items
No Milestone
Assignees
Clear assignees
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: vikunja/vikunja#1812
No description provided.
Delete Branch "%!s()"

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?