calbzam

Yes, from our JIRA guide: https://www.plasticscm.com/documentation/extensions/plastic-scm-version-control-task-and-issue-tracking-guide User name and Password: Specify the JIRA credentials used to log into JIRA and log the changes. If you use Atlassian Cloud, the User name must be the email address of the account, and the Password must be an API token. You can find out how to generate API tokens for your Atlassian Cloud account in their official documentation. Note that these fields can be the user credentials in JIRA, or the credentials of a different JIRA user specifically created to log Plastic SCM changes. The issue history on JIRA will display the change as coming from the user configured here. - If you are removing the "issuetracker" folder, please close the GUI first so the folder is not locked. Could you attach the Plastic client logs so we can review the error? I've just set up a JIRA cloud organization and everything seems to be working if I use the API token. If you reach us at support @codicesoftware.com, we can arrange a GoToMeeting with you to debug your scenario. Regards, Carlos.

Hi, Could you open a ticket at support@codicesoftware.com including your registered account at www.semanticmerge.com? We will manually generate the trial license for you. Regards, Carlos.

But the changes are already committed in a changeset in the branch? And then this issuer switches the workspace to this changeset but the files are not downloaded? Not getting any specific error? My only guess is this user has configured some "cloaked.conf" rules preventing the files to be downloaded. If you have a commercial license, you can open a support ticket and we can even arrange a meeting with you to debug. Regards, Carlos.

Hi, In the Plastic preferences panel, under "Other options", you can configure the "Pending changes" view to track changes only when the file content changes (but default, it only checks if the timestamp has changed). Regards, Carlos.

Just as an update for this thread, after configuring the Plastic server to use "Active Directory", the users were properly resolved. Regards, Carlos.

Hi, By default, all users can access the system. If you are getting a "User unknown" error, it seems that the user you entered cannot be resolved in the LDAP (or the server authentication configuration is wrong). In there was a permissions error, it would be different message. More information about how you can assign permissions in Plastic: https://www.plasticscm.com/documentation/security/plastic-scm-version-control-security-guide We would need to review the Plastic server debug log, to better understand the error. You can reach us at support@codicesoftware.com and arrange a meeting with you to debug the issue. Regards, Carlos.

You can reach us at support@codicesoftware.com. Regards, Carlos.

Hi, Removing the "C:\Users\xxx\AppData\Local\plastic4\issuetrackers" folder and re-configuring the JIRA parameters in the GUI doesn't help? We may need to arrange a GoToMeeting session to review your setup. Please reach us at support@codicesoftware.com. Regards, Carlos.

Hi, Are you exporting a git repo via "git fast-export" and then importing to Plastic via "cm fast-import"? It seems to be a problem with the export package. Are you exporting a public repo or a package you can share with us? Regards, Carlos.

Hi, I'm trying to reproduce but it seems there is a problem with https://bitbucket.org at the moment (I can't log in) :$ Are you replicating from a Plastic repo to a Bitbucket git repo, right? Regards, Carlos.

Ok, thank you very much for the update. I was not aware of theseJira's Next-Gen projects. We will need to adapt the plugin to fix your reported issues and being fully compatible with them. Regards, Carlos.

Ok, so the problem is the JIRA settings are not properly saved and when you reopen the GUI the values are not there? Are you configuring JIRA for all repos or for one specific repo? I will try to reproduce. Regards, Carlos.

Hi, You will need to configure your Plastic server to use your desired authentication mode: https://www.plasticscm.com/documentation/administration/plastic-scm-version-control-administrator-guide#Authenticationconfiguration Then you can create custom users and groups also from the webadmin. Once you have the Plastic users and groups, then you can assign the permissions for your users: https://www.plasticscm.com/documentation/security/plastic-scm-version-control-security-guide Please let us know if you face any issue. Regards, Carlos.

Hi, You can just replicate all your cloud repos to a local machine. But If you want to setup a backup server in your office, you will need to buy a Team edition license for that purpose: https://www.plasticscm.com/pricing Installing and configuring the hosted Plastic server is a very straightforward process: https://www.plasticscm.com/documentation/installation/plastic-scm-version-control-installation-guide Please let us know if you need more help. Regards, Carlos.

Hi, All the locks should be already released. Could you confirm? Yesterday, we had a temporary issue in our cloud: Regards, Carlos.

If you are able to "Save file as...", it means the revision content is correct in the database, so something should be preventing the file to be downloaded during the update operation. Could you check if there is a cloaked file in one of the following paths? 1) Workspace path. 2) C:\Program Files\PlasticSCM5\client 3) C:\Users\xxx\AppData\Local\plastic4 4) Do you have a "plastic-global-config" repo where you distribute a "cloaked.conf? Regards, Carlos.

Hi, When you replicate the parent repo, it's not necessary to also replica the Xlinks. The problem is the parent repo will have pointers to the Xlinked repos so if you try to run an update in the replicated repo, you will get an error reporting that the Xlinked repos cannot be reached. Regards, Carlos.

Hi, We may need to arrange a GoToMeeting session to debug the issue. The key is understanding why the conflicts determined by Plastic doesn't fit with what you see in the different merge contributors. You can reach us at support@codicesoftware.com Regards, Carlos.

Ok, let me understand the issue. You switch your workspace from the branch explorer to a specific branch but some files are not downloaded? Switch to the same branch in a different machine, are the files downloaded? Regards, Carlos.

Hello, Please give a try to the following workaround, and let us know if it worked.The errors are due to a missing icon in your current GTK icon theme (as the error messages say). One workaround is trying to install a new theme, we can also try to change the icon theme using the gtkrc-2.0 configuration file.1) Navigate to /usr/share/icons2) List the directory content. For me, the content of /usr/share/icons is:Adawaita, HighContrast, Humanity, Humanity-Dark, LoginIcons, default, hicolor, locolor, ubuntu-mono-dark and ubuntu-mono-light.3) Create a file in your $HOME with name .gtkrc-2.0 and the following content:gtk-icon-theme-name="Humanity"If you don't like the Humanity icon theme, or you don't have it available, you can choose other theme changing "Humanity" for any of the icon themes you have in /usr/share/icons.4) Save the contents of .gtkrc-2.0 and restart gtkplastic. Change the theme if the error persists. Regards, Carlos.

Ok, sorry. If the artist is using Plastic GUI, if he/she opens the branch explorer --> browse repository in this changeset --> select the file --> Save revisions as. Are you able to save the file revision in your disk? If a different artist from a different workspace runs the same update, are you reproducing the issue? Regards, Carlos.

Hi, If the artist, is using Gluon, they can customize the files to download via the "configure" button. If a file/folder is not configured, it won't be downloaded when you run an update. Please review in the "configure" panel if the file appears to be configured and if after selecting the file, the artists is able to download it. I guess other artists/developers are not affected, right? I mean they all can download this file. Regards, Carlos.

Could you attach the Plastic client log? C:\Users\carlos\AppData\Local\plastic4\logs\plastic.debug.log.txt If you rename the "plastic4" folder and reconfigure the Plastic client, does the issue persist? Regards, Carlos.

Could you attach the full client logs for the user having the issue (and if possible a user not having the issue)? (you can also send it to support@codicesoftware.com). I guess there is not an external tool (antivirus...) removing the content of this folder, right? It's a bit weird that the issue is only happening to one user in your team (I guess you are using, the same Plastic server, connecting to the same server...). The user who faces the issue could create a local "ignore.conf" in the workspace so you don' t need to commit the file to the repo. Regards, Carlos.

Hi, Are you using the cloud? In that case: "issuetrackers/organization@cloud/myrepo". Yes, you export multiple independent repos or "allrepos". I attach the template "jira.conf". Regards, Carlos. jira.conf