Windows GUI: The pending changes view is now autorefreshed when it gets the focus, as requested in our UserVoice: Auto Refresh Pending Changelist Option. A new option has been added in the "pending changes view" options dialog to enable/disable this feature (disabled by default).
Windows GUI, macOS GUI and Linux (GTK) GUI: Now, the JIRA issue tracker extension is able to change the status of the associated issue to a branch / changeset based on a changeset comment. To do so, you can define your own keyword-status mappings: if the keyword is present on the changeset comment, the issue status will be changed to the defined status. The format of the mappings is as follows:
One example of this is:
[FIXED]-Ready for QA|[WONTFIX]-Done
If your changeset includes in its comment the keyword "[FIXED]" (with the brackets), your issue status will change to "Ready for QA". Bear in mind that the transition between statuses must be allowed by your JIRA workflow.
To configure this in Windows, you can go to Preferences > Issue Trackers > (JIRA configuration) > Status transitions.
To do the same on macOS or Linux, you must open your jira.conf file and add the following line, replacing the value:
Name=Status transitions;Value=[FIXED]-Ready for QA|[WONTFIX]-Done;Type=Text;IsGlobal=True
This feature works binding issues to both branches and changesets. It is NOT necessary to have the Plastic SCM custom field ID set for this to work.
This feature closes the following UserVoice request: Jira integration should be able to transition issues through Jira workflow and maintain all data
Working on LDAP authentication mode, the proxy server could fail with the error 'Object 'SecurityHandler' has been disconnected or does not exist at the server.'. Fixed
When a shelve that contains a file that matches some "lock.conf" rules, the apply shelve operation was failing with the error 'The file XXX requires exclusive checkout, but it is not up-to-date in your workspace'. Fixed
Gluon: The "Undo changes" context menu option in the "Explore workspace" view didn't persist the workspace changes: the previous file contents were properly downloaded but the "controlled" state was lost when Gluon was closed. Fixed.
When there were path permissions defined on the repository, The 'apply shelve' operation was failing with the error 'You are working with out-of-date objects. Maybe your client or workspace is out of date, please update it.'. Fixed
The USN journal Change Tracker service was not installed properly if the PlasticSCM server was not installed. Now it's fixed.
JIRA extension: while building the necessary Uris to access the JIRA server, the extension was deleting the path were the JIRA server was running at. For example, if JIRA was running at https://myserver/jira, the extension would use only https://myserver to build the Uris. Fixed!
Linux (GTK) GUI and macOS GUI: if the gtkgui.conf / macgui.conf configuration files had an invalid workspace set as current, you were prompted with the "First use" welcome dialog even if you had perfectly valid workspaces in your plastic.workspaces configuration file! Not anymore ;)