Consistent Sequential Date Order for Recurring Tasks in past
J
Jean-Philippe Ghyoot
Currently, when a task with a past due date is marked as recurring, the next date assigned does not follow a sequential date order but reverts to the next date after the present. This behavior is inconsistent as subsequent tasks are created sequentially for future dates.
Suggested Improvement:
Modify the recurring task functionality so that the next date assigned follows a sequential date order, even when the initial task has a past due date. This would ensure consistency in task scheduling and better alignment with user expectations.
Implementing this change would streamline task recurrence and provide a more intuitive user experience.
J
Jean-Philippe Ghyoot
Hi Jon,
Thank you for your follow-up. Here are my responses to your questions:
- Impact on Task Management:
This issue arose while attempting to building an accounting CRM. When the service start date is in the past (common in catch-up jobs), automating task creation with the past date as the start and then adding a recurring action to the task triggers this problem. The system doesn't maintain the intended sequence for recurring tasks.
- Preference for Current Functionality:
I believe changing the functionality to follow a sequential approach, both for past and future dates, would be beneficial. The current behaviour doesn’t seem to offer any advantage that would be missed.
- Frequency of Encounter:
This issue occurred specifically when building a use case for the accounting CRM. It hasn’t been a frequent problem, but addressing it would prevent potential future inconsistencies in task management.
Jon Darbyshire
Hey Jean-Philippe Ghyoot, thanks for your feedback! I have a few more questions for you:
- Can you provide a specific example of how this issue has impacted your task management?
- Are there any specific scenarios where you would prefer the current functionality to remain as is?
- How frequently do you encounter tasks with past due dates that are marked as recurring?