It would be great to have a way to set what data is carried across when recurring tasks are made, like you can when you duplicate a task. For example, I am creating recurring tasks by month but depending on the plan, the times will need to change so I'd like the task to recur without the time estimate so this can be planned on a monthly basis.

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.