I would like to configure a project with the allowed tasks ahead of time and then whenever a task is created, it must be one of the tasks provided on this list.
These tasks should continue to be sorted by task type (e.g. fx_fire is an fx task type).
I would like the task project definitions to be first class citizens so that I can query the project configuration or the shot configuration of a particular task. I have plans to tie tasks/task categories into the layering order of our USD workflow and this will then tie into that potentially.
You can think of the tasks as assets and a shot task as being an instance of that asset, if you like.
If it is too much of a burden to create tasks on the project first, before making them in shots, you could potentially make a mode that will author a new project task from the same dialog for certain permission types.
I want to eliminate areas where artists or coordinators need to enter strings by hand. At scale it is a virtual guarantee that we end up with slight deviations in spelling (tire_burnout or tyre_burnout), or spaces (spiderwebs or spider_webs), or capitalization (SpiderWebs or Spiderwebs). These inconsistencies make it much more challenging to build automation templates or track same-things across/between projects for forecasting the cost of certain tasks.
Discord conversation here: https://discord.com/channels/517362899170230292/1528631102762127490/1530456273873797151
Thanks
Ben
