Update Task Template behaviour query/request

Hi All,

I have a question about the update task templates behavour…

Say I have two shot task templates where one is a subset of the other. e.g. they both have “comp” in the “Comp” Step, but only one has “anim”. I decide to the update the task template on a shot from one to the other.

The UI that pops up will flag that ALL of the existing tasks on the shot don’t match those in the new pipeline step, even those with the same name and step.

My options are to delete them or leave them there. Neither option really works for what I’m trying to do which - expand the task list on the shot - if the shot is already in progress, deleting them will orphan publishes and break user path caches. Keeping them gives me a duplicate to tidy up.

I guess my question is - do I have that right - is that the intended behaviour? If so, would it make sense to have another ‘merge‘ behaviour that would keep existing tasks that match name and step?

Thanks!

1 Like

It totally makes sense! We use our own tool to update the Tasks from the Task Templates for this very reason.

1 Like

Same here! A merge option would be :fire: