We've had requests from clients to support these features, and I'd love to get feedback about the way you'd all envision them working. I put these two features together in this post as the main challenge for both of them is determining the scope: If you set shot code to be unique, is that globally unique across all projects, just within a project, just within a sequence, or within some other container (episode, scene)? How would you want to use it?
Maybe you can check a Unique box in the field config, and then also be able to choose a another field on the same entity that sets the context (none for global, Project for within the project, etc). That could also work to set asset names to be unique within their asset type or version names to be unique within their shot. Can you think of any cases that wouldn't cover?
Auto-incrementing has the same scope issue, and then additionally might need options like the starting number and the increment to increase each time (if it's not always by one). Would that cover the range of uses you can think of?
Thanks for your input!