It would be useful to add the various 'Show selected branches ... in diagram' from the 'Branch Explorer' tab as a context menu to the table of branches on the 'Branches' tab.

It can be hard to find the branches of interest in the explorer, but the filter for the table view makes this much easier. The table already helpfully maintains your current selections when you change its filter, so it is easy to build up the group you want.

As far as I can see, the GUI is missing the useful --ignore options from the command line.

This would help people learn syntax i think.

The tree view in Pending Changes gives a much better overview/visual structure to the things that were modified. However, per default everything is always collapsed. So for each new change one needs to click-open every single hierarchy level by hand, to reach the assets that were actually changed...

All other tree views (Items, Branches, ...) are affected similarly, and would greatly benefit from such a hotkey.

I suggest to use Alt-click, as for example, Unity uses that same method to selectively and recursively collapse/open subtrees. 

Basically a shortcut to take one of the 3 versions (source, base, destination) as a result one.

Described in more detail in the end of http://www.plasticscm.net/index.php?/topic/1200-exception-during-3-way-merge-when-pasting-big-text/

Need a client silent Install with chosen components in active directory

You should add a way to shelve a already checked-in changeset. This way a checkin on the wrong branch could be shelved, deleted and then applied to the correct branch.

Sometimes when looking at a code review making comments against individual lines is not appropriate. The implementer might have got the design/architecture or pattern wrong. It would help to be able to record a comment at a top level against the review to allow an audit trail without having to go through all the line by line comments. For example. Design and implementation ok, no security has been considered and there are weaknesses so needs rework. Minor code comments as recorded, but review abandoned due to high level issues.

I know this was the default behavior a couple of versions ago, and it was extremely advantageous for our team because we tend to have a lot of files (XML data and such) that get changed but we don't intend to preserve those changes.

We had been in the habit of checking in only our relevant changes, and it's been a big change to our workflow to have to either undo all pending changes first, or deal with the merges that ensue. If there was an option to prefer the old behavior it would be a big help!

A workspace update can be quite slow, particularly if you made a mistake in cloaked.conf. Rather than killing the process, it would be nice to be able to cancel the update.

"Xlink changes cannot be commented" - that message shows up when you try to comment a change in an xlinked file (in a code review). IMHO it would be much easier if xlinked files could be commented just like other files.

This is a very useful feature for diffs with long lines.

Now that we have matching inside a line, this would be a natural follow up. With this, there would no longer be any need for horizontal scrollbars in diff view.

I really miss the drag and drop functionality that most Windows programs have such as Perforce. I'd like to be able to drag files from a windows explorer window to a changelist etc.

This would make merges much slicker, by saving all of the RMB clicking.

It would be great to see all attributes set on a branch somewhere else then the 'attributes' panel. Not I have to change the side panel from 'Properties' to 'Attributes' to see which attributes are set on a given branch.
To speed this up, it sure is nice to see attributes in the branch tooltip.
What you'd say about that?

As a developer, I can specify what is the type (text/binary) of file with a given extension. But, I want PlasticSCM to immediately apply these settings to the current workspace (only new files are affected). Also, it would be convenient that a filetypes.conf placed in the root dir of repository to have the same effect for this specific repo, on the top of global settings (as for ignore.conf).

Provide a mechanism to approve merges into specific branches.
One option is to use pull requests with an approval mechanism (of one or more required approvals).

This will allow trace-ability and enforcement of organization rules.
Linking it to code review will make it even greater.

(Check out Stash for examples)