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.

It would be great if whenever actions are done in Plastic Cloud that all pertaining partys are automatically emailed (with a configuration for this).

Example, I create a code review for user A,B,C. Lookup user A,B,C's email and shoot them a notice of the code review. This is a standard feature for other cloud base repos that is super useful. Currently i have to either rely on my teammates telling me they submitted code reviews or have each of them integrate an app into their setup. It would be nice to have a one stop shop for this. : )

A comment of an attribute cannot be changed now (even copying to clipboard is not possible).

A commit message text box and a code review text box does not have any scroll bar, does not allow scrolling with a mouse and does not allow Ctrl+A (select all text). All these things would be useful.

This suggestion has been added here already (https://plasticscm.uservoice.com/forums/15467-general/suggestions/4341465-checkin-comment-and-code-review-text-boxes) but it was marked as completed even though it is still not working.

See also the original post here: http://www.plasticscm.net/index.php?/topic/1291-some-ux-issues/#entry10137
There is also another suggestion close to this explained by a picture (partially displayed lines).

I would like to see a way to group workspaces (and repositories) in order to make the list more readable.

As i use the model one workspace for a project or component, i got to many for a readable list.

Tagging them with a keyword and show them as a tree would make it easier to find workspaces.

There was already a suggestion of this kind:
https://plasticscm.uservoice.com/forums/15467-general/suggestions/5657638-add-option-in-pending-changes-to-tell-plasic-that

But the solution is not very convenient. If we do a refactor there may be a lot of added/deleted items. I simply want to select a pair of added/deleted items then open context menu and select "repair move" or anything equivalent. I already know what has been moved and want to mark this explicitly. Tweaking the similarity so Plastic will find the added file is too complicated.

Look that this beautiful theme you have for MacOS - https://www.plasticscm.com/download/releasenotes/7.0.16.2815

Please get me that for windows.

The pending changes / branch view is burning a hole into my eyes.

This would help people learn syntax i think.

This would require making the commit window non-modal..

Need a client silent Install with chosen components in active directory

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.

Create a plastic scm server plugin for Synology NAS to allow the server to be easily hosted on a NAS drive.

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

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.

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/

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!