-
-
Notifications
You must be signed in to change notification settings - Fork 239
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
repeat every day until
decrements end date on task completion
#2897
Comments
I found this bug report, which is definitely related: #1818 Fixing that issue probably fixes this one too; however, it may be possible to fix this case without having a general fix for the rrule parser, by copying the |
Hi,
See this section of the documentation, which links to the exact issue you quoted - #1818: So, could you please say in what way exactly this differs from #1818 - what extra work does it require the differs from that issue, in order for this one not to be a duplicate? Many thanks. 😄 |
My apologies, the Tasks syntax is often so intuitive that I don't need to check the documentation 🤦 If it's an undocumented feature, I think it makes sense to wait until #1818 can be fully resolved. I'll close this issue. Thanks for the great work on this plug-in! |
Hi Arne, thanks for your understanding. |
I appreciate your including the text, but for future reference, there isn't enough information in this "Steps to reproduce" to do anything useful in investigating this issue. |
Please check that this issue hasn't been reported before.
Expected Behavior
If I add the following repeating task
and I complete it, I expect Tasks to create a new instance with the same end date and tomorrow as the due date.
Current behaviour
The end date is decremented in both the completed and the new task:
If I complete one more, the old completed task is left alone, but the newest two are again decremented:
Steps to reproduce
The task from the screenshots above was:
Which Operating Systems are you using?
Obsidian Version
v1.6.3
Tasks Plugin Version
v7.4.0
Checks
Possible solution
No response
The text was updated successfully, but these errors were encountered: