Status Overrides For Versions from Different Asset Parents

[Robinson]

It would be really useful if status overrides could be assigned to Versions based on their Asset Parent

 

 

For example:

 

CG workflow is very different than Comp workflow, and the former feeds into the latter; so we use different statuses on versions from each.

 

ex.  

Modeling Task Version (On an asset) : Ready For Review -> Noted -> Lead Artist Check -> Ready For Comp -> Approved: For Final

Final Comp Task Version (On a Shot) : Ready for Review -> Noted -> Lead Artist Check -> Approved: For Temp -> Approved: For Final -> Uploaded: Temp -> Uploaded: For Final -> Client Final -> Tech Noted -> Delivered 

 

Currently these statuses all live in the same drop-down and it would be cleaner and more intuitive if overrides could be built just like the task overrides.

 

 

Thanks,

 

Andy

[Carl Claesson]

Hi Andy,

 

Thank you for the feedback!

 

Would it make sense to have this override based on the type of the version instead of the parent?

 

For example if you have a version of type "Comp" it would have: Ready For Review -> Noted -> Lead Artist Check -> Ready For Comp -> Approved: For Final

 

Regards,

Carl

[Robinson]

Hi Carl,

 

Absolutely, putting this on the type would accomplish the same goal.  

 

While we are at it, the ability to name or label the overrides in the schema would also be useful i.e. "CG Override" "Admin Override" etc. 

[Carl Claesson]

Hey,

 

I've added two internal feature request tickets for this.

 

Thank you for the feedback.

 

Cheers,

Carl