Todo Events don't use the status field #1616

Closed
opened 2026-05-07 19:25:59 +02:00 by leuckeju · 4 comments
Member

PersonalTodo objects have the status field. It has semantically correct possible values for state (probably ical defined?), such as Needs action, Completed and In Process.

However, the implementation does not use this data attribute, e.g. moving the slider to 50% will not change the status to In Process and checking the box to complete a todo does not set the status to Completed.

I believe this issue stems from the fact that the current data model for todo completions (the slider and checkbox) predates the addition of the status field in calendarevents. This seems however still at least unintuitive how it is set up currently.

PersonalTodo objects have the status field. It has semantically correct possible values for state (probably ical defined?), such as `Needs action`, `Completed` and `In Process`. However, the implementation does not use this data attribute, e.g. moving the slider to 50% will not change the status to `In Process` and checking the box to complete a todo does not set the status to `Completed`. I believe this issue stems from the fact that the current data model for todo completions (the slider and checkbox) predates the addition of the status field in calendarevents. This seems however still at least unintuitive how it is set up currently.
Author
Member

mentioned in issue #1302

mentioned in issue #1302
Author
Member

assigned to @leuckeju

assigned to @leuckeju
Author
Member

mentioned in merge request !3904

mentioned in merge request !3904
Owner

mentioned in commit f9adfc7c10

mentioned in commit f9adfc7c101c636ab8dd7c970ecbe316907d454a
Sign in to join this conversation.
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
aleksis/AlekSIS-Core#1616
No description provided.