Technical environments for implementation & testing

Currently we are using the Workspace feature of Monday.com for two purposes:
- Functional: organization of differents departments, projects and teams.
- Technical: we have one environment for implementation and testing.
Even though, Monday has not been designed for the second function. The issues and limitations are as follows:
1. There is no version control. No mechanisms are designed to keep different versions of a certain development. Only the Duplicate feature is being used for that purpose.
2. The system does not behave different for a Test than for a Production environment, so technically all Workspaces/Environments are the same.
3. There is no promotion mechanism. Once a development is tested and ready to be put into production, the only mechanism to promote it is to use the Duplicate feature once again, having to manually move all objects between Workspaces.
4. Environments/Workspaces cannot be synced or duplicated. Objects (boards, dashboards, etc) must be synced or duplicated one by one.

Sadly no answer to this topic. A similar request from Feb 23 also has gathered 0 answers so far.

It looks like staging environments and change control are not really something that the average monday.com customer is into. Which makes me wonder whether the platform is actually ok to use for anything but trivial cases / non-critical data…