This is a major bug in your product and it literally stopped our team to switch from git to plastic scm. I was trying out your product for the first time and after creating a project I invited my colleague to work together with me and she was not able to join my server. She was also checking out plastic scm and she did not join organization but instead created one. Later she was not able to join my organizaton even after several attempts. She tried to logout but she couldn't because that feature was not present in the GUI. She tried uninstalling nd reinstalling but still she was logged in. Finally she lost hope. You must definitely add an feature to logout and login from the windows application and also fix the joining organization after skipping it in login page.

(The following text is specifically about read-only xlinks. I am not sure if it applies to writable xlinks as wel.)

When I use Plastic, I expect that the contents of an xlinked folder in my workspace is updated at the same time that the xlink itself is updated. Plastic currently requires me to perform a workspace update to download the changes. Me - and everyone else on my team - find this behaviour counterintuitive. I would like to see the following changes in behaviour:

1. When I create or modify an xlink, I would like that Plastic update the xlinked folder contents immediately, rather than require me to create/modify the xlink locally, check it in, and then update the workspace.

2. When I receive an xlink modification as part of merging from another branch to my current branch, I would like that Plastic update the xlinked folder contents immediately, instead of waiting for me to click "Update Workspace".

Reason for change 1: The need to check in the xlink before receiving the new files locally makes it impossible for me to verify the consistency of parent repository + xlinked repo together before checking in.

Reason for change 2: The need to click "Update Workspace" to update the xlinked folder contents means that the "merge from branch X" operation in the UI does not actually guarantee that my workspace includes the changes from the other branch; merge + update is necessary, but only in situations where xlink changes are part of the merge.

Change 2 also means that I can freely choose how I introduce or modify a new code module that most of the team wants to maintain as a separate entity: either by duplicating the code module's files into the current repository, or by xlinking to another repository containing the module. Without change 2, there is a hidden cost to using an xlink: Everyone else on the team that has a work branch in flight will need to click "Update Workspace" after they have merged my in my changes to a work branch, or else it will appear to them that some source files are missing / out-of-date related to my changes. They do not care that I happened to use an xlink, they just expect that after a merge, their workspace is up-to-date (like it is in 99% of cases when merges do not include any xlink changes).

Hello, when pushing changes to a git repo the author field is the plasticscm username with no email. The git author field is formatted as "User Name user@email.com". It would be nice if on the push/pull dialog screen, there was an entry for the user to enter a proper git author value to the commits that are being pushed. This will allow for software like gitea and github to properly recognize the user who is the author of the commit. Below is an example of a git commit done with PlasticSCM:

commit 001c43bcfcff911feb2eb87887de484f7d089e8e
Author: jburkert <>
Date: Tue Dec 22 14:06:03 2020 -0800

changed readme

You can see the email is empty and name is the PlasticSCM user name. Below is an example of a git commit done from git-bash:

commit 21fb401cab3517c00db7ba09e45c41bfd233dad6
Author: John Burkert bj.59191@konamigaming.com
Date: Thu Jan 9 17:33:08 2020 -0800

updated readme links to new server

You can see the author name is not a user name and the email is present.

Thanks,
John

Sometimes, two members of my team change the same Unity Prefab in different commits. This leads to a conflict when merging. It also triggers an error message - the merge tool can't open the file.

This is different from code-based conflicts (Plastic's Merge Tool opens, and works well).

If I fix the merge conflict before attempting to Auto Merge (i.e. right click on the prefab asset, and select "use mine" or "use theirs"), everything works as expected.

It would be nice if Plastic brought up a more helpful error message. Something like "we're working on a merge tool for [insert file types], but in the meantime, here's what to do..." Telling a user that the merge tool crashed can lead to confusion about the true cause of the problem.

For reference: Plastic SCM Cloud 9.0.16.4567 + Unity 2019.3