By default, Studio proposes the same location to store file-based projects and GroupShare projects alike.

For supportability and traceability reasons, our translators are expected to download GS projects to a uniform location which is different from the out-of-the-box default as proposed by Studio. Some translators also occasionally work with file-based projects which they are expected to store in a different location (not to be mixed with GS projects).

Out-of-the box, Studio proposes to save all projects in <user_profile>\Documents\Studio 2017\Projects\<project_name>. This path continues to be proposed by default each time, unless and until the user creates a new file-based project in a different location. The last-created project path becomes the new default. 

The path entered manually in the Open Trados GroupShare Project wizard does not stick. Instead, either the out-of-the-box default or the last-created file-based project path is proposed. This frequently results in saving GS projects in incorrect locations. Even if there is no human error, our users find it frustrating to have to change the path carefully each and every time they open a new project. 

We have found a workaround to trick Studio into keeping the desired path: start the ‘Create new project’ wizard; enter the new path; click Next and then simply cancel the wizard. As a result, the selected path will stick as the default project location for GS projects, but only until the next time the user creates a file-based project in a different location.

Our idea: The project location for GS projects should stick automatically and independently of the path for file-based projects. Alternatively, a user setting for GS project location could also be a good solution.

Best regards,
Pawel