Hi,
We have a monthly checklist that contains c200 tasks all assigned and dated. We often add new tasks monthly to our workflow and include the new assignee and date for completion. When it comes to rolling forward the checklist for the next month, I set the latest project as a template and create a new one based on that (this allows me to set a new start date). This way I know we are always using the latest list of tasks and assignees.
The problem is, the new project inherits the template projects complete/incomplete status for each task, so I have to go through “uncompleting” each task. Is there a setting I am missing?
I can not think of a use case where a new project based off a template would need to inherit the completion status (I would have assumed the process would simply ignore this meta data).
I know there are are numerous ways to have recurring checklists but here are my thoughts as I understand them:
Blank Project Template or Template upload:
- If we add a new task in the current month we need to ensure we add to template project or file
- Can’t set a new start date and have everything shuffle along correctly
Duplicating Tasks:
- Doesn’t work so well with multiple dependencies
Any thoughts or recommendations hugely appreciated.
J