You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Today when I started Planify, I suddenly got a bunch (10 or so) of 'overdue' tasks that have already been completed a few months ago, around August and September mostly. I did not do so manually and nothing else in the database reverted or went corrupt.
All the tasks in question were subtasks of the same parent task. I've had this occur once before and this was also the case then.
To Reproduce
I'm not sure exactly what triggered this, but I can explain what I did:
Have a parent task with a bunch of subtasks.
Mark most as completed.
Restart Planify (at some point in the future).
The tasks have been marked as undone.
Expected behavior
Subtasks that are done don't get marked as undone.
Desktop (please complete the following information):
OS or DE: [e.g. pantheon, unity, gnome]: GNOME 47
Version [e.g. 0.1.2]: 4.11.6
Additional context
Investigating the database, I see that all these subtasks in the Items table have had the completed_at field set back to empty, and checked is also now marked as 0. I still have a backup of my database from last week and they are all marked correctly with completed_at filled in and checked set to 1 there.
The text was updated successfully, but these errors were encountered:
Describe the bug
Today when I started Planify, I suddenly got a bunch (10 or so) of 'overdue' tasks that have already been completed a few months ago, around August and September mostly. I did not do so manually and nothing else in the database reverted or went corrupt.
All the tasks in question were subtasks of the same parent task. I've had this occur once before and this was also the case then.
To Reproduce
I'm not sure exactly what triggered this, but I can explain what I did:
Expected behavior
Subtasks that are done don't get marked as undone.
Desktop (please complete the following information):
Additional context
Investigating the database, I see that all these subtasks in the
Items
table have had thecompleted_at
field set back to empty, andchecked
is also now marked as0
. I still have a backup of my database from last week and they are all marked correctly withcompleted_at
filled in andchecked
set to1
there.The text was updated successfully, but these errors were encountered: