Hey @Bobby_Goldstein ,
I think the solution you’re looking for isn’t in Sections, nor in pre-multi-homing, but in Custom fields.
The reasons are this:
- Although you can add a section to a task (Subtask Sections (aka Subsections) - The Hidden Story) it will not merge with sections in your template, assuming it has them.
- You can group by custom fields project templates (Saved Views in Project Templates is here!)
- When you use a Custom library field, the value you give to a subtask will be carried over to the value it will have in the template, and thus grouped accordingly. You can set the custom field value in the rule that adds the subtask, under “show more” in the detail pane when you edit the subtask.
The only downsides are that:
- Saved views don’t show until you actually use the template
- Grouping doensn’t maintain manual sorting
If you want to force the sorting, you can utilise a number field for that. Also add that field to both the the pipeline project and the template.
If you still have trouble making this work let me know, and I’ll DM you a calendly link for troubleshooting.