We may have a 'comp' task at the shot, sequence or project. Do I have to define three comp tasks, one for each of them? Can I have a one-to-many relationship for a task template?
Date
Votes
2 comments
-
Don Parker Hi Kay, that's an interesting scenario. Currently, our Tasks can only be linked to a single parent, so you would need to make 3 different Tasks. Do you think that's awkward? If you could link a Task to more than one thing (a Shot and a Sequence), would that artist know which thing the Task was for? Tell us more about your workflow and maybe we can brainstorm a good approach (which may mean we have dev work to do!).
-
KP ask Templates can only apply to a single entity type at the moment so you would have to create your Task Template for say Shots, and then duplicate that Template and change the entity type to Sequence. Duplicating the Task Template will duplicate the template and the Tasks that are a part of it so a lot of the work will be done for you.Where this gets tricky is if you are assigning Pipeline Steps for your Tasks as most users do. Pipeline Steps being the way Shotgun groups up Tasks for a particular pipeline (like your Shot pipeline). These Pipeline Steps are unique per entity type since Assets, Shots, Elements all have a different workflow. So when duplicating your Task Template, you'd just have to ensure the same Pipeline Step exists for the new entity type or re-assign the Pipeline Step to something appropriate for your new entity type.Agreed it is a little extra work to initially setup your Task Templates so they apply to multiple entity types like that. But once you've setup one Template, duplicating it for your other entity types shouldn't take more than a couple of clicks at the moment.Task Templates can only apply to a single entity type at the moment so you would have to create your Task Template for say Shots, and then duplicate that Template and change the entity type to Sequence (and then again for Project). Duplicating the Task Template will duplicate the template and the Tasks that are a part of it so a lot of the work will be done for you.
Where this gets a little tricky is if you are assigning Pipeline Steps for your Tasks as most users do. Pipeline Steps being the way Shotgun groups up Tasks for a particular pipeline (like your Shot pipeline). These Pipeline Steps are unique per entity type since Assets, Shots, Elements all have a different workflow. So when duplicating your Task Template, you'd just have to ensure the same Pipeline Step exists for the new entity type or re-assign the Pipeline Step to something appropriate for your new entity type.
Agreed it is a little extra work to initially setup your Task Templates so they apply to multiple entity types like that. But once you've setup one Template, duplicating it for your other entity types shouldn't take more than a couple of clicks at the moment.We will look into supporting this but as Don mentioned, please let us know more about your workflow! We'll see if we can come up with something cool.
Please sign in to leave a comment.