Develop a JIRA plugin for Jira, to improve visibility.
Add options to create branches from JIRA and issues from PlasticSCM.
Embed links to open each other Web Portal.

In general, a text box in the Jira issue is not enough. The interaction should be smooth.

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

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/

Consider the following branches:
1(root)
1-1 (branch from 1)
1-2 (another branch from 1)

Currently, you can checkout and check-in the file on branch 1-1 and you can also do it on branch 1-2, as long as both checkouts are in their own branch head changeset and not at the same time.

So when branches 1-1 and 1-2 merges back into the root branch 1, you get a conflict.

The idea is to have types of files that cannot be merged, never, completely exclusive for all branches, the same way it is done in lock.conf for a per-branch basis.

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

This info is missing from both the label list and the trigger.

The only way to get the branch name from a label is to perform a two step operation: Check on which changeset it is set and then look for that changeset branch (in the changeset list).

Just like the "advanced merge to", allow the user to cherry pick to any branch.

This allow the user to avoid switching to the branch he want to cherry pick to, which can be very time consuming (reimporting workspace in a game engine for exemple).

Need a client silent Install with chosen components in active directory

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!

This would help people learn syntax i think.

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 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).

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.

Hi,

Since the latest release it's possible to close the tabs in the caption area.

Great feature but I would like one more enhancement, a non closeable tab (preferably the first tab on the right) that contains non workspace related subtabs like Your Workspaces, Your Repositories Rss Notification and Sync replication (not sure about Shelves).

This way the workspace related tabs stay cleaner (and smaller).

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.