blue

Hi @toddhd, Have you installed the right edition of plastic SCM? Let's follow up via ticket, we will need to take a look at the logs. Please create a ticket via -> https://plasticscmsupport.zendesk.com/hc/en-us/requests/new

Hi @GardensSiobhan, The Component is available only for on-prem. Currently updating attributes via server REST API is not available. Sorry for the inconvenience.

Hi @WilmiRosa, Thank you for reaching out to us. It seems like you are in a similar situation with this thread. Can you please confirm the version of plastic SCM used and check if the issue persists in both New GUI and legacy? Does the issue occur only for specific types of files?

@nuFF3 Please open a ticket via https://www.plasticscm.com/support --> Create New Ticket. Let me take a look at further from it.

Hi @nuFF3 , If the status of items become check-out after updating, it might be related with unresolved conflict. Do all of the items appear as check-out in the pending changes? Can you please check if you have any unresolved conflict? cm unco --help The command above will help you find the un-checkout command. Please open a ticket via https://www.plasticscm.com/support and share the screenshot of Pending changes and Branch Explorer.

@AidanPuche Let's follow this via ticket, please contact us at support@codicesoftware.com

@Tinyfish Do you have profiles configured for both dst repo? Let's follow this via ticket, please contact us at support@codicesoftware.com

@AidanPuche Can you please share the error message you have received?

Hi @dwicks As your local directory does not have information for the paths. You can try to get the information from the cloud. cm ls / --tree=3@yourRepo@yourOrg@cloud --format={path} -R The command above will print path of the file in a specific changeset(3 in the example). -R is for recursive. For the more information, please execute the command below. cm ls --help Please let us know if you have any questions.

Hi @hiros, @deab This version https://www.plasticscm.com/download/releasenotes/11.0.16.6979 includes the fix of the issue. Please let us know if you have any questions.

Hi @hiros, The issue is known issue and our team is working on it. The fix will be delivered in the future release and you can check the release note from Plastic SCM download page.

Hi @tahomasan, This error can be related to the restrictions on GitSync. Can you please take a look at the link I have attached and check if this is relevant to your situation?https://www.plasticscm.com/documentation/gitsync/plastic-scm-version-control-gitsync-guide#GitSyncrestrictions Please check if the issue persists when you attempt to gitsync with clean new repo.

Hi @TimeDog, Let's follow this via ticket, please contact us at support@codicesoftware.com

Hi @freaksed In order to have default comment for users, you could use a "before-checkin" trigger. The trigger could parse the checkin comment:https://www.plasticscm.com/documentation/triggers/plastic-scm-version-control-triggers-guide If you need a default comment only for your checkin only and you are still using legacy plastic SCM GUI, then you can configure default Comments in Preferences. Please take a look at the link and let us know if you have any questions.

Hi @mhardy, If everything is set up properly, please make sure that the new PC workspace is on the latest Changeset. Thanks,

Hi @Colin - Stacking Chairs Thanks for waiting for the response. I have investigated if there are other ways to do it. cm help archive When you run this command, you should be able to see the information about the archive. The following is from the command. Please try with the command above which specify the specific changeset number.

@Larsson24 Have you deleted items and checkin the changes? If you are using centralized workspace, with the checkin, the changes should be reflected to cloud. Please assure that there is the latest version of project in plastic SCM dashboard.

Hi @Colin - Stacking Chairs, If you like to free up some space in the cloud, here's the link you will be interested in it. Please let me know if you have any questions.

Hi @fract, Here is a link you might be interested. If the software installation is already completed, Step-by-step guide is the first document you would like to read. Cheers,

Hi @Oleg, I'm afraid it's not possible to go back to Collab. You can find more information in here --> https://blog.unity.com/games/upgrading-from-collaborate-to-unity-plastic-scm I hope you find this information useful.

Hi @Oleg The ignore rules only affect private files (not files that are already under source control). I assume that you tried to add checked in file to ignored list. If you want to remove specific files that already in source control, you will need to manually do it: eg. selecting them in the GUI --> right-click --> Delete(Do not delete items on disk). Then, Add to ignored list button will be enabled. Deleting files : https://www.plasticscm.com/documentation/labs/main#Lesson3-Moving,deletingandrenaming ignore.cof: https://blog.plasticscm.com/2014/11/configuring-ignored-items-on-your.html I hope you found this information useful and please let me know if you have any questions.

Hi @Welton Sorry for the delayed response! There's global configuration in Plastic. This way, all the Plastic clients have the same settings by default. This means that the configuration files will consult the global configuration and the local (workspace relative) and main (client relative) files. However, Changeset colors - User is not applicable for global configuration. What can be globally configured? Only the filters and conditional format rules can be globally configured. The user-specific configuration, such as displaying full branch names, merge links, the start, and end date, will always prevail from the local configuration file. If these settings are set globally, they will be ignored during the "merge" of global and local rules. Click here to learn about global configuration.

Hi @Engstrom, Thanks for reaching out. Installing new version of Plastic SCM will not overwrite access to existing repo. Here's the page you might want to refer. You can invite the users from cloud panel if you are using cloud organization. Plus, the art team might find Gluon useful. Thanks,

Thanks for the update @Garrett, The "Option" can be used for both Changeset and branch but I am afraid that I cannot confirm if you are on option for branch or Changeset. Could you please check if you can see attributes when you click Attributes from Other Actions(see the screenshot below)?

Hi @Garrett, Thank you for reaching out. If you want to migrate from Github repository to Plastic cloud, GitSync is an option for you. The link you refer should be working for you to remove the connection. To assist you better, could you please let us know what steps you follow to migrate from Github to Plastic Cloud? Cheers,