Bug Description
What's the bug?
When marking recurring tasks as complete ("mark completed for this date") in normal note view / kanban view, the complete_instances array records yesterday's date instead of today's date, while normal task completedDate fields work correctly.
Steps to reproduce:
- Create a recurring task (e.g., daily task with
FREQ=DAILY)
- Mark the task as complete, either direct click or using right click, "mark completed for this date", results are the same
- Check the
complete_instances array in the task's frontmatter
- Observe that the date stored is yesterday's date instead of today's
Expected behavior:
The complete_instances array should contain today's date when marking a recurring task complete today, matching the behavior of completedDate for normal tasks.
Actual behavior:
- Normal tasks:
completedDate shows the correct date ✓
- Recurring tasks:
complete_instances shows yesterday's date ✗
Screen Recordings: (See the dateModified property with the actual correct time)
https://github.com/user-attachments/assets/bdbee3b2-eba5-4e85-8519-8ccf69078a3d
Additional context:
My timezone: US-East
Time when bug occurs: just past midnight
I am not sure if it is somehow related to this issue here #574
Bug Description
What's the bug?
When marking recurring tasks as complete ("mark completed for this date") in normal note view / kanban view, the
complete_instancesarray records yesterday's date instead of today's date, while normal taskcompletedDatefields work correctly.Steps to reproduce:
FREQ=DAILY)complete_instancesarray in the task's frontmatterExpected behavior:
The
complete_instancesarray should contain today's date when marking a recurring task complete today, matching the behavior ofcompletedDatefor normal tasks.Actual behavior:
completedDateshows the correct date ✓complete_instancesshows yesterday's date ✗Screen Recordings: (See the
dateModifiedproperty with the actual correct time)https://github.com/user-attachments/assets/bdbee3b2-eba5-4e85-8519-8ccf69078a3d
Additional context:
My timezone: US-East
Time when bug occurs: just past midnight
I am not sure if it is somehow related to this issue here #574