Feature Requests

Please search first before posting to help others find and vote for your idea!
Multiple Improvement Suggestion for Recurring Tasks
Recurring tasks reliability is crucial for task management, for example when use to manage monthly deliveries, to-dos, bills, etc. Current state of recurring tasks is rather confusing to use and not very reliable. Most common issue I have encountered myself is it will skip months when recurring, tasks not recurring immediately after making solved etc. Here are some improvement I believe is rather simple to be implement but will make it more usable and reliable: Whenever clickbot recur a task, show details output that include the new due dates and previous due dates, (and start date if set), this instantly make it easier to double check the recurrence is done properly. The recurrence of the start date should be customizable, or at least make it recurring properly in relative to the due date. For example when the due date is set on first day on month, but the start date are set at 7 days prior, it should maintain that whenever it recur Fix weird bug in windows client where the task are not recurring immediately after marking solve, it requires me to close the app in task manager completely and start again. Allow us to select when a tasks is long due expire, it will still recur at the same frequency even though the new due date are still in expire. Right now the behavior is if you have a monthly recurring task let's say 1st Jan 2010, when you marked as solve it will set new due date to 1 March 2025, the time I writing this, instead it would be great if we can choose to recur at the same frequency, meaning after making it solve, it recur at 1st Feb 2010. Fix the color coding for expires and non-expires tasks (This is quite useful for certain work that deal with monthly deliveries and we fall behind schedule by months, or just for bills payment reminder in general)
0
Custom Field Selection for Recurring Tasks
Currently, when the recurring option is enabled, all custom fields are maintained for each recurrence. However, there is no option to select specific custom fields to persist, which creates challenges in cases where only some fields need to remain unchanged while others vary. Example Use Case: Consider a list used for transaction history with the following custom fields: * Category * Payment Method * Amount For a subscription with a variable amount, the Category and Payment Method remain the same each month, while the Amount changes. Currently, when enabling the recurring option, all custom fields are retained, requiring manual updates for fields like Amount every time. While this is manageable with three fields, our setup involves seven custom fields. This requires resetting fields unnecessarily, adding extra effort each month. Proposed Solution: Introduce an option to select specific custom fields to persist when setting a recurring task. For example: Allow users to choose Category and Payment Method to remain unchanged while leaving Amount as editable for each recurrence. Benefits: * Reduces manual work for tasks with multiple custom fields. * Improves efficiency for users managing recurring tasks with variable values. * Provides greater flexibility and customization in task recurrence workflows. Alternative Workaround: Currently, the workaround is to maintain all custom fields and manually update the necessary fields (e.g., Amount) after each task is created. However, this is inefficient for lists with many custom fields.
0
Load More