Numerous issues exist with the project layout system:

1. If you have two environments and you use the "Import Layout" feature to copy the layout from one to another, it does not accurately copy over the positioning of services/groups. This occurs even if both environments have the same amount of services, or even the exact same copied over services.

2. If you manually edit your services layout, then refresh the page, it moves around services to positions they were not at when it was manually edited. It's as if it has a mind of its own.

3. If you use the auto layout, it is inconsistent in it's positioning, and will stack almost everything vertically the majority of the time, along with adding massive gaps between groupings.

1. If you duplicate an environment, create a service in one of them, then create a service in the other and use the same name as the service your created in the previous environment, it will say that there already exists a service in this environment with that name. Even though the services are in different environments.

Proposed fixes/expected results:

1. Services and groups that exist in both environments should be mapped to the exact position as their counterparts. Services that only exist in one environment should prompt the user to manually select a position for it. This way there is no random guessing involved in the positioning, nor any fancy algorithms to place the service, which seem to be unreliable for the most part.

2. Pretty self explanatory, basically all changes made to services positioning should save across page refreshes.

3. The Railway team can most likely come up with a better auto layout solution than I can, and can most definitely come up with a better solution than the one currently implemented. It should just be clean and reliable.

4. Duplicate name checking should not exist cross-environments.

Thank you.