I would suggest following the route that you're describing and where possible - keep the assignments at the project level for the users and then in the template have the 'Assigned Role' and then if you have any qualifiers that might differentiate 'which' PM still in the template itself.
At it's core - even if you tried to do this with a Pipeline, you still need all of these components in the template anyway so the Pipeline would know who to assign anyway. So one way or another if you're assigning the users at the Project Level - then the template still needs to be set up to know which people on the Project are responsible dynamically.
I will always advocate for using Formulas over Pipelines in this case because 1) once the Pipeline runs - its not going to run again so if you need to reset the assignments then you'd need another pipeline to update etc and then 2) a Formula just gives you more flexibility if you need to carve out exceptions or overrides as time passes. Just my two cents though.
Hmm, I have more doubts now.
So, I have a task template table, and I create tasks associated with the project depending on the project's stage using the pipeline. However, there is no relationship between the Task Template table and the Jobs table.
Are you suggesting the use of formulas instead of a pipeline?
I understand that if I have the "assigned to x role" in the project record, then with the pipeline, I could populate the "assigned to" field in the tasks based on the role. Perhaps I'm not grasping it fully; if you could provide further clarification on this concept, I would be grateful.
The pipeline will help me to create the task, associated with the project, when the Proyect is changed to that corresponding stage, but the "Assigned to" will be a formula and not be populated by the pipeline itself?
Thanks!
