Setting progress causes the item to be marked as done instantly #1681
Labels
No Label
dependencies
duplicate
help wanted
invalid
kind/bug
kind/feature
needs reproduction
question
security
wontfix
No Milestone
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: vikunja/vikunja#1681
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?
Description
Setting progress on a task causes the task to immediately getting marked as done. After marking it undone, the task keeps getting marked as done a few seconds later.
Vikunja Frontend Version
0.22.0
Vikunja API Version
0.22.0
Browser and version
Firefox 121
Can you reproduce the bug on the Vikunja demo site?
No
Screenshots
No response
Is that reproducible consistently across all browsers?
If you can't reproduce it on the demo, that might indicate it's already fixed (the demo runs the last unstable build).
Thanks for your reply, Konrad.
Do you see any problems, updating a production server running 1.2.2 to the latest unstable?
I can reproduce the problem with at my colleague's computer and mine, both running Firefox 121.
For testing purposes I've created a snapshot, upgraded to the latest version, reloaded the window until it told me to reload the window, and then I still can reproduce the problem. After which I restored the snapshot, so we're running 0.22.0 again.
Do you mean the
:latest
docker tag? That's the latest release (which is 0.22). Useunstable
for the mentioned unstable build.I use the package as downloaded from the mirror. I rather configure things myself.
Ah, you are referring to the word "snapshot", I was referring to the LXC snapshot, so I could instantly restore to the previously configured state.
Which package did you use? Can you provide a link?
Or better yet, what is the exact version string (from the "about" dialogue in the frontend or the
vikunja version
command on the server) you tested this with?Sure, I'll gladly repeat it for you. :-)
Okay, so you tested both times with 0.22 instead of the unstable build one time?
First time with 0.22, then with unstable and now back to 0.22
We could reproduce the problem everywhere.
Which unstable version did you test?