Skip to main content

Predefined/Enumerated Task Names/Labels

Feature requests PipelineCommunity

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

Posted by Ben Andersen
4 comments

Log in to comment and vote

Comments4

  • Mustafa Zaky Jafar

    Team

    Hey I was testing something and I wonder if you can give it a test.

    In the project anatomy below task types section, you can add multiple FX tasks. and you can give it any name you want e.g. FX Fire ,FX Cloth, FX Smoke, FX Destruction.

    Then Check the entity naming setting in project anatomy where you can select only one.

    The option selected in the screenshot above will result in FX Fire → fx_fire .

    Then when creating a new task, the task type/task name we added above will be used as it for the task label. And, for the task name, it’ll be generated on the entity naming above.

    This will effectively have the following result

    • Ben Andersen

      Yeah… the only thing is that I like being able to make broad categorizations of tasks by department/contribution layer. I want to be able to add data that applies to all fx tasks, not applied (and kept in line manually) separately to fx_fire/fx_smoke/fx_destruction/fx_whatever.

      • Ben Andersen

        Also, I generally just don’t want anyone to have the ability to type anything into the label field at all (or any other field that is part of the normal work operations)

      • Mustafa Zaky Jafar

        Team

        I believe what you are looking for are

        • Have multiple labels for tasks. which should be added in the tasks section in project anatomy.

        • Disable editing fields: label and name.