You weren’t asking me, but they resonate with me! I explain this to clients all the time–sometimes you want a project template, and sometimes you can use Duplicate project. It’s unintuitive that there’s not just one way to do it, but if you can internalize the features and use cases for both, you can handle most cases well.
1 Like
@Richard_Sather I hadn’t considered the functional difference between grouping and sections - that makes a lot of sense. We ended up going back to sections for our ‘waterfall’ project template and it works fine.
I noticed one other feature that was harder to access when using groups - when multi-homing a task, you can choose the project section within the originating project. If grouping by sections, one would have to go down to fields, show fields from other projects, and choose the custom field value for the intended grouping.
However, this might not be an issue for optimally configured projects, according to the ongoing vs waterfall project configurations you’ve shared.
Thanks for the reply! Very helpful.
1 Like
Thanks @as_an_android , glad to hear it has worked out for you!
A very valid point indeed! But this can work great when multi-homing tasks between projects that share the same fields, such as ‘Type’ for example or a common ‘Status’, so if they are both grouped by that, then you don’t worry about which Section they will go into, since you are grouping both projects by the same field.
For more on waterfall (deadline-bound) VS Ongoing projects, you may want to have a look at this guide that I recently posted:
This guide is great! Thank you