drekbour We have an ez template deploy job using the choice parameter "DEPLOY_ENVIRONMENT", that is available for developers, support and operations. The Choice parameter for some jobs implementing the template allow deploying artifacts to developer environments. However, I also have some jobs implementing the template that is hidden away and only available to support and operations that have production environments in the list of choice parameters. Ideally, we don't want every job inheriting the template to sync the choice parameters list or the order. Is there a way to exclude the choice parameters from syncing up with the parent template?