Guys, most of the usability recommendations you made are being applied to the new GTK and Mac GUIS :-) They'll soon be on Windows too.

My typical usage scenario is to "prepare for the next task" - so I generally want to switch to the branch explorer and refresh it so I can see the work others have done. I may also want to create a new branch for a new task while the current one is committing. I don't actually want to modify the current check-in/workspace, but I may want to review other change set comments/history to see what has been done. Currently, I just get "stuck" waiting for my own commit, sometimes up to a minute.

Here are a few things I'd like to be able to do while a commit or update is in progress.
1) Activate a different workspace and switch to a branch
2) Switch to the branch explorer and perform a refresh to see potentially new content from other users.
3) review comments or Extension data (e.g. Jira extension data)
4) Add attributes to a branch (not necessarily the one I am committing on)
5) Perform change set/history searches

Hi Diego and Jakub,

switching between workspaces is the only operation I can think it's interesting, at least "safe". I mean, continue working on the same workspace that is committing changes to the server is some kind of unsafe idea....

Please elaborate a little bit the idea :P

I think they suggest to allow continue working while an update is running in a background. There is a very similar suggestion here:
http://plasticscm.uservoice.com/forums/15467-general/suggestions/3917314-allow-user-to-change-workspace-tabs-during-an-upda

Hey guys, but this already works this way... I mean, except when you've to checkin just under 5 files, otherwise it is always launched on a separate thread...

I agree - anything to make the GUI tool more responsive if you are working on multiple things... like looking at other branches while you have it switching to a specific branch.

I really would like this!
Not only for check in, but to update, switch to this workspace, replication... :)