ollieblanks

@Wolfram, Thanks for giving us this feedback. I have to argue that this is not a bug, as the feature you are referring to is named "Changeset Colors", so these colors should only apply to the changesets within the Branch Explorer view. I cannot argue that having two colors assigned to each user is not intuitive at all, and we should unify these somehow. I'll bring this up with the Product Management team as I believe your suggestion of decoupling this feature from the Branch Explorer and expanding it to the whole application is a fantastic idea.

Thanks for sharing your reasoning behind requiring this option @Wolfram. I have logged a task with the Development Team for this to be added. Watch this space!

This is a brilliant point! Thank you for raising it. I will share this with our Product Management team.

@eldaville, this is a very old thread that is unlikely to be related. Please log a support ticket with a Problem Description of the issue, and we will be happy to help you figure it out.

Unfortunately, there has not been much movement on this as this would require a significant overhaul of how the full Plastic SCM client works under the hood (as it is changeset-based and not file-based like Gluon). The suggested workflow with binary files where you need to see the lock status would still be to use the Gluon GUI or manually with the cm listlocks command. That being said, there have been advancements that have increased the likelihood of this feature being feasible. It is a highly requested feature, and we do not plan to just ignore our users feedback, so thank you for sharing.

Quite right that you are confused by this, the diff does seem odd. As @tucny suggests, can you share the sources of these files for review?

Thank you for providing this feedback. I can assure you that you are not alone with this request and it is something we plan to address in the near future! For now, the latest version can be downloaded from www.plasticscm.com/download.

Unfortunately, this is not currently possible, but this would make a great addition. I will share this with the Product Management team. Thank you for sharing!

Hi @Bernie Roehl, sorry for the delay in response. Plastic SCM is a pay for what you use service. If you need to add more than three users, please do so, and you will be invoiced for the amount of active users for that billing period. If a user is inactive during a billing period, then you will not be charged for that user. Hope this helps!

Hey @KristofMorva, These are not dumb questions! Thank you for raising them. The Unity Dashboard is just a new improved dashboard. Users are welcome to continue using both, or just the one. This functionality is already available for existing users too. You just need a Unity ID to access it. Hope this helps!

Hey @trx, Your assumption is correct. Hope this helps!

Hey @bob, The Pending Changes view itself is a representation of the diff of your workspace contents with the latest changeset. This view is slightly more feature rich in the Plastic SCM client than it is in the Version Control package (at this time) so I urge you to try this view in the full client. Hope this helps!

Hey @Luth, It sounds like you were using the legacy Unity integration that was superseded by the Version Control package in Package Manager. I urge you to give the Version Control package a try as it had all the features of the legacy integration plus more! Hope this helps!

This error usually means that path permissions have been configured and the user does not have the correct permissions for the paths they are merging. Hope this helps!

Can you be a little more specific? If you want to change the user that the server is running under then you can change the user that runs the service.

Hi, Within your workspace folder will be a hidden .plastic folder which links it to the current repository, if you want to make this folder a new workspace pointing at a new repository then you will need to delete this folder. Hope this helps.

If you are using an older version that did not receive this fix, then performing the exact same merge should bring you right back to where you left off. Hope this helps!

Hey, 8787 is the port number, as stated in the error message. Hope this helps!

Self-hosting your own Plastic SCM server is only available via the Enterprise licensing option. Hope that helps!

Hmmm... it seems this specific operation cannot be performed from the GUI, but it can be performed using the CLI by navigating to the folder you want to check in and performing the following command: cm checkin . --applychanged Hope this helps!

Hi, Does UnityYAMLMerge.exe exist in the location reported in the error message? I suspect that it doesn't and you need to reconfigure your Merge Tools via Preferences > Merge Tools. Hope this helps!

In your scenario, holygk@cloud should be the correct input for Source Control Provider URL. If you are still having issues, please log a support ticket and we can investigate further for you. Hope this helps!

Sorry for the delay in response. The command for checkin is cm checkin. The command for updating the workspace would be cm update which can be invoked with the --forced parameter to force all objects to update to the latest. Please note: You can add --help to any command and it will give you detailed information about how that command can be used. Hope this helps!

It seems that a merge has corrupted that YAML file. Do you happen to know the steps you have taken to produce this behaviour? It seems odd that the issue would persist even if reverting to previous. Can you revert back further to pinpoint exactly when this happened? Hope this helps!

Hey @Joshuan sorry for the delay in getting a response. I believe you are probably getting a discount from migrating from Collaborate. Please check your recent invoices as that will give you a more detailed description of the discounts applied. Hope this helps!