Probability score: 0.7  

Question improvement suggestion: Provide specific details about the version of the Apply Studio Project Template plugin you are using and any error messages encountered when trying to use it with cloud projects.  

In the meantime, based on the information you have provided, here is a suggested answer to your question:  

Hello Angelo,  

Thank you for bringing this issue to our attention. It seems that you are experiencing challenges with the Apply Studio Project Template plugin in relation to cloud projects. Here’s a step-by-step approach to address your concerns:  

**Step 1:** Understand the Current Limitations  

Currently, the Apply Studio Project Template plugin does not support cloud projects, which is why you are unable to restore settings from local projects when working with cloud projects.  

**Step 2:** Workaround for Settings  

As you mentioned, the workaround is to manually update the QA Checker settings for each project after downloading it from Trados Team. This is indeed a temporary solution until the development team resolves the defect CRQ-43404.  

**Step 3:** Future Updates  

You can keep an eye on future updates from the development team regarding the plugin's compatibility with cloud projects. It is possible that enhancements will be made to allow the plugin to function with cloud projects in upcoming releases.  

**Step 4:** Utilize Cloud Project Settings  

Remember that cloud project settings take precedence over local project settings. You can modify these settings directly in your cloud account through the browser, which may help streamline your workflow.  

**Step 5:** Feedback to Development Team  

If you feel strongly about the need for the plugin to support cloud projects, consider providing feedback to the development team. User feedback can often influence the prioritization of feature updates.  

I hope this answer addressed your question. If not, please reject the answer, add the question improvement suggestion information, and click the RWS Community AI checkbox on the right to try again.  

RWS Community AI

Step 4: it is not true, as the settings in Trados Studio are set, but everytime somebody downloaded the project from the cloud, the settings are getting lost.
I use the latest version of the plugin

Hi Angelo Caltagirone , thank you for reporting this, I'll add this to the board and review with the team.

Hi Angelo Caltagirone , The Apply Studio Project Template plugin was originally developed specifically for local Studio projects, at a time when Trados Cloud was not part of the workflow. As a result, the plugin does not currently fully support updating the settings of cloud-based projects, due to architectural differences between local Studio and Trados Cloud projects.

At this point, extending the plugin to support cloud projects constitutes a new feature and will require an initial technical investigation to assess feasibility and scope before any commitment can be made.

Our development team is currently prioritizing other areas, therefore not actively adding new features to this plugin ourselves. However, because this is a community-driven, open-source project, we would welcome contributions from any developers interested in implementing this feature for Trados Cloud support.

If you or others in the community would like to contribute:

• The source code is available here: Apply Studoi Project Template
• If you’re interested in getting involved, I’m very happy to help answer questions, support your work, and review pull requests!  my github handle is Impertatore or contact me via e-mail: phartnett@rws.com 

Patrick Andrew Hartnett 

As for GroupShare projects I am recently working on, there are just very few settings in such project, which the user could adapt. The only settings I have access to are translation memories and termbases.There is also a setting for match repair, but that's really all. So no QA or other useful settings. The only way to have your own settings there is to create your own project with the sdlxliff files from the GS project.

Hi Jerzy

This is because you get to use GroupShare as a user with restricted rights. I use it as admin and the plugin works very well with GS projects.
Kind regards,

Angelo

Hi Patrick Andrew Hartnett 

I am aware that this is not a priority for the development team. What should be a priority is to fix the bugs (reported in September) in synchronizing settings from Trados Team to Trados Studio. It is really time consuming to change in every project the settings about termbases and TMs, as they are not synchronized. That is why I thought that using this plugin could help me until the bug is fixed (I am very sad to report that bugs in Trados Team are not solved rapidly as in Trados Studio, even if it would be much faster as there is no desktop release to prepare, they could fix it and implemented fast in the web).

I am not a develper, I have enough to do with facing new challanges in our industry. I surely could learn and contribute, but I do not have time for that, sorry. So I hope either the developers fix the bug as soon as possible or someone else is taking the challenge and redevelop the plugin for Trados Team. But I do not think that someone will do it, as it a very specific plugin that few users use.

Thank you anyway and kind regards,

Angelo

Hi Angelo Caltagirone ,

I completely understand your frustration and appreciate your feedbak. To clarify, the issue described in CRQ-43404 is being addressed separately by another team and specifically relates to the synchronization of project settings between Trados Team and Trados Studio.

The Apply Studio Project Template plugin, on the other hand, was originally developed for local Studio projects. It doesn’t currently integrate with cloud-based projects due to key differences between local and cloud workflows. Extending the plugin to support Trados Cloud projects would therefore be a new feature rather than a fix for an existing defect.

Currently, our team is focused on maintaining compatibility of community plugins with new product releases, while new features or large functional changes depend on available capacity and community involvement. As this plugin is open-source, we welcome contributions from anyone interested in extending it to support cloud workflows.

You can find the source code here: Apply Studio Project Template GitHub repo
If anyone in the community wishes to take this on, I’d be happy to offer guidance, answer questions, or review pull requests. My GitHub handle is Impertatore, or you can reach me at phartnett@rws.com.

Thank you again for sharing your feedback, Angelo, it’s always valuable for us to understand how these issues impact real-world workflows.

Hi Patrick Andrew Hartnett 

I understand completely, but as I already mentioned, I am not a developer and I cannot rewrite the code for this plugin.

And today I have received an e-mail from support, telling me that the problem will be solved in the next major release of Studio, wich means mid next year (I suppose Studio 2026). Which means manually change settings for all projects until the next release of Studio, thousands of projects that have to be set manually. A major waste of time and reduced productivity.

Sorry, I know it is not your fault, but this is becoming more and more frustrating, working with Trados Team. If I had known, I would have stuck with GroupShare, but now it is too late.

Kind regards,

Angelo

Hi Patrick Andrew Hartnett 

I understand completely, but as I already mentioned, I am not a developer and I cannot rewrite the code for this plugin.

And today I have received an e-mail from support, telling me that the problem will be solved in the next major release of Studio, wich means mid next year (I suppose Studio 2026). Which means manually change settings for all projects until the next release of Studio, thousands of projects that have to be set manually. A major waste of time and reduced productivity.

Sorry, I know it is not your fault, but this is becoming more and more frustrating, working with Trados Team. If I had known, I would have stuck with GroupShare, but now it is too late.

Kind regards,

Angelo