Is it recommended to have Parent Instance and Child instances on different versions in Team Development?DescriptionIs it recommended to have Parent Instance and Child instances on different versions in Team Development?Release or EnvironmentAll ReleasesResolutionThe answer to that question is a No. It is expected that the sub-development instances are on the same software version as the parent development instance. The way we suggest to set up a Team Dev environment is as follows: 1. Have a parent development instance on the same software version, such as Madrid, as the target instance, such as production. 2. [Recommended] Clone the production instance to the parent development instance. 3. Provision sub-development instances on the same software version as the parent development instance. 4. (Optional) Log in to the parent development instance and clone it to the sub-development instances. 5. On each sub-development instance: *Define remote instance connections to other instances in the hierarchy that this instance needs to push and pull with. *Select the parent instance. *Pull all changes from the parent instance. *Grant access rights to appropriate developers. The parent instance must be on the same release family as the local instance. For example, a development instance on the Madrid release family must have a parent instance also on the Madrid release family. If you select a parent from a different release family, the Team Development dashboard displays an error message and prevents you from pulling changes and reconciling. If you select a parent from a different patch release, the dashboard displays a warning message but allows you to pull changes and reconcile. Additional InformationIn addition to the above information, please find below a useful documentation that is helpful https://docs.servicenow.com/csh?topicname=t_SelectTheParentInstance.html&version=latest