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

Repeated tasks don't respect the start time of the next day setting #3378

Open
Raindrac opened this issue Sep 1, 2024 · 1 comment
Open

Comments

@Raindrac
Copy link

Raindrac commented Sep 1, 2024

Your Environment

  • Version used: 9.0.6
  • Operating System and version: Linux & Android
  • Desktop Environment: Gnome 46

Expected Behavior

Let's say that you change the start time of the next day setting so that a new day begins at 5am. You schedule a daily task (e.g, make the bed) at 2am, and you set it to repeat every day. You wake up on August 8th around noon and Super Productivity recognizes the beginning of a new day, so it automatically creates any relevant repeated tasks.

The next scheduled time for the "Make your bed" task would be August 9th at 2am. Because you set the day to begin at 5am, the day would begin at August 8th at 5am and end on August 9th at 5am.

Because 2am on August 9th lies between August 8th at 5am and August 9th at 5am, you would expect that it would be recognized as part of that day and that Super Productivity would automatically create the task.

Current Behavior

Super Productivity doesn't consider a task scheduled on August 9th at 2am as part of a day that you've configured to span from August 8th at 5am to August 9th at 5am. For that reason it won't be created until the next day, and by that point the task is already overdue.

Steps to Reproduce (for bugs)

  1. Create a task and schedule it for the next day at 2am
  2. Set it to repeat daily at 2am
  3. Open your settings and change "Start time of the next day" to 5 for 5am
  4. Disregard the current instance of the task because it's already created
  5. Wait until when the next instance of the task is expected to automatically get created
  6. Observe that isn't automatically created on the day that it's expected to
  7. Wait another day, and observe that the task is finally created after it's already overdue

Can you reproduce this reliably?

Yep!

@Raindrac Raindrac added the bug label Sep 1, 2024
Copy link

github-actions bot commented Sep 1, 2024

Thank you very much for opening up this issue! I am currently a bit overwhelmed by the many requests that arrive each week, so please forgive me, if I fail to respond personally. I am still very likely to at least skim read your request and I'll probably try to fix all (real) bugs if possible and I will likely review every single PR being made (please, give me a heads up if you intent to do so) and I will try to work on popular requests (please upvote via thumbs up on the original issue) whenever possible, but trying to respond to every single issue over the last years has been kind of draining and I need to adjust my approach for this project to remain fun for me and to make any progress with actually coding new stuff. Thanks for your understanding!

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

No branches or pull requests

2 participants