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

Request: Allow scheduling annual chores on same day every year #817

Closed
Germs2004 opened this issue May 3, 2020 · 1 comment
Closed

Request: Allow scheduling annual chores on same day every year #817

Germs2004 opened this issue May 3, 2020 · 1 comment
Milestone

Comments

@Germs2004
Copy link
Contributor

Currently, when we add an "annual" chore, the help text on the page says "This means the next execution of this chore is scheduled 1 year after the last execution". So if I schedule a chore for Jan 1, 2019, but actually execute the chore on Feb 8, 2019, then the help text looks like Grocy will schedule the follow chore for Feb 8, 2020.

This request is to add a checkbox called "always repeat on this specified schedule." When this checkbox is checked, then this chore will be scheduled for Jan 1, 2019, and Jan 1, 2020, and Jan 1, 2021. Even if the chores are executed late, the followup chores should still be scheduled for the same date as originally scheduled.

@berrnd berrnd added this to the vNEXT milestone Feb 9, 2022
@berrnd berrnd closed this as completed in 0d1f2ad Feb 9, 2022
@berrnd
Copy link
Member

berrnd commented Feb 9, 2022

Sorry being late here. You're right, makes totally sense - and the Yearly period type is also just the same as using Daily and a period interval of 365 days.

So the Yearly period type now does exactly what you thought of, schedules the chore on the same day each year (based on the new start date, ref #1612).

All existing Yearly chores will be automatically migrated to Daily on the upgrade to the next release.

grafik

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

2 participants