We have more than 150 recurring tasks and multiple resolved comments on it. It gets very messy each time they are recreated. A feature that doesnt make sense I believe. Why should I want a resolved comment to be reassigned?

Totally agree this is not making a lot of sense. We also create new tasks when something is recurring because we want to track time estimates to keep an eye on the workload. It is very frustrating that assigned comments get back as unresolved. Leaving all comments out is not an option because we want to see what happened to a task in the past.

I agree also...this is a huge time suck every month for me as I need to re-check 100's of assigned comments that were resolved. They go back YEARS....it's very frustrating. They were resolved for a reason, please leave them that way!

We too like to have a record of previous tasks so not creating a new task doesn't work for us. Would definitely like to see the status of the comment (resolved or unresolved) retained when creating a new task.

'Assigned Comments' should not become unresolved on a reoccurring task. I'm so glad other people had the same problem! This seems so easy to change and that so many people would benefit from it.

TLDR: There is no way to choose it to be either way, it just makes all 'Assigned Comments' unresolved upon any task reoccurring. As a simple solution, it would be significantly better even if it was just reversed to retain whatever resolved status it had. With no way to choose it to refresh/reset. This makes even more sense when you realize the Checklist section behaves in the exact same way. It's redundant, and makes them almost the same in regards to a reoccuring task situation. Currently, neither can be permanently resolved without deletion or unassigning the comment, which both options remove the timestamp and leaves a team wondering if it was actually completed.

Solution: Now, if one feature did reset to unresolved (Checklists), and one feature didn't reset and retained it's resolved status (Comments). That would be very a simple change and create a ton of flexibility in the way reoccuring tasks can be used. This gives you the added benefit of a resolved comments history to scroll through on the next monthly/weekly reoccurred task! Keeping when/who completed what on last month's task. As it is now, a bunch of "Unresolved" tasks that were already resolved last month, will pop back up overwriting it's resolved version if it existed. The lack of this (like the OP said), makes 'Assigned Comments' to a Team really unusable. That is, if you are using any reoccurring tasks for monthly or weekly work. Which has to be extremely common.

I think 'Assigned Comments' would be perfect for the unpredicted tasks, while keeping a beautiful running history of things that've popped up. Plus 'Comments' are already used for collaborating and for adapting to change within a Task!

'Checklists' can remain the same for the standard predictable tasks you already know you'll have to get done each period of time. It can keep refreshing with each month, and act as a clickable standard procedure for completing that monthly task. Lastly, since this allows people to utilize and view the 'Comment' history to see patterns of things that have come up on the past Tasks. They can then use that to modify their Checklists/Procedures to improve them, all without leaving that same relevant Task.

Hey Rachel! thats actually a good call out. Follow up question, do you have the create new task button checked or unchecked?