Repeated Task does not change Deadline property to the current day/time plus the current repeated interval when Done
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 28
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
### Search first
- [x] I searched and no similar issues were found
### What Happened?
see title
### Reproduce the Bug
1. Create a new Task with `\Todo` and name it "Do a test"
2. Click on the item to see the detail view
3. Show hidden properties
4. Set Deadline to next hour (e.g. 13:00) and Repeat to 1 Hour
5. Set Status to Done
6. The Deadline changed to previous Deadline + Repeat time (e.g. 14:00) instead of current time + Repeat time (e.g. 13:32 when current time is 12:32)
Same with Scheduled instead of Deadline.
### Expected Behavior
The documentation sais:
> When `Status` changes to `Done`, the `Deadline` (or `Scheduled`) property changes to the current day/time plus the current repeated interval. For example, if it's currently 12:20 and the interval is 1 hr, the new value is 13:20.
https://github.com/logseq/docs/blob/master/db-version.md#repeated-tasks-and-nodes
### Files
_No response_
### Browser, Desktop or Mobile Platform Information
NixOS 25.11.4137.72ac591e7370
Flatpak, version 2.0.0
### Additional Context
_No response_
### Are you willing to submit a PR? If you know how to fix the bug.
- [ ] I'm willing to submit a PR (Thank you!)
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the steps with a repeated Deadline and then with Scheduled. Compare the behavior with the repeated-tasks description in db-version.md, and trace the Status-to-Done handling. Done means both properties use the current time plus the configured repeat interval rather than the previous value.
Written by the indexing model from the issue text.
Assessment
- Domain
- database
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100