Skip to content
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

It should be possible to base the next recurrence of an event on the time it was done #53

Closed
schemar opened this issue Apr 30, 2021 · 8 comments · Fixed by #502
Closed
Labels
type: enhancement New feature or request

Comments

@schemar
Copy link
Collaborator

schemar commented Apr 30, 2021

It should be possible to base the next recurrence of an event on the time the original event was done - instead of the time the original event was scheduled.

Todoist supports that with the ! operator (i.e. using every! instead of every). We could do the same.

@schemar schemar added the type: enhancement New feature or request label Apr 30, 2021
@Skefflock
Copy link

Skefflock commented Aug 6, 2021

Hello.
Thanks for such a great plugin.

My question is: what I see is a bit opposite of what you described in this issue. Exactly behavior I need is when a task recurrence counts its period from the original due date. But what I get is the alternative variant, where task is recurring base on the done date.

image

The screenshot below would make even more mess.
image

No matter if due+period is less or greater than today, it still counts from the done date (which is always today)
image

Have I found some bug or I am I doing anything wrong to get the expected result?

@schemar
Copy link
Collaborator Author

schemar commented Aug 7, 2021

Hmm, good point. Thank you for reporting this. Which version of Tasks do you use?

@Skefflock
Copy link

1.2.0. The latest.

@schemar
Copy link
Collaborator Author

schemar commented Aug 7, 2021

Thank you. I opened #261 as a separate issue to track the bug.

@andtheWings
Copy link

andtheWings commented Aug 8, 2021

+1
To remove ambiguity, perhaps the task modal could ask you to check whether you want recurrence calculated from last due date or last completion date. One of these two options would have a parenthetical saying (default). Then in the Tasks Plugin menu, the user can mark which they want to be the default behavior.

P.S. This plugin is really cool! Thanks for developing it!

@stixard
Copy link

stixard commented Nov 4, 2021

+1 for this request

@therden
Copy link
Contributor

therden commented Jan 7, 2022

@schemar I totally understand that you don't have time to work on this now.

If and when you do, I'd love to see support added for either

  • a flag to indicate whether a particular recurrence rule is to operate "by due date", "by done date", "latest of due or done date", or
  • (if Dataview-style fieldnames:: triggers are ever supported in place of emoji triggers) different types of recurrence rule fields (like bydue::, bydone::, bylatest::).

@pcause
Copy link

pcause commented Jan 24, 2022

I've seen the notion of a a strict recurrence. if you put a date of 2 weeks it recurs every 2 weeks from completion. if you have a strict recurrence when completed it would be scheduled 2 weeks from the due date. I strict occurrence is indicated by having a + in front of the date in todo.txt format. so rec:2w is a recurrence from complete and rec:+2w is a recurrence from original due date

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants