We want closer of the operating system Windows 7/8 to the standard. Therefore we would use like a variable to pack it in the user directory. Unfortunately, StarTeam allows only absolute paths. It would have even the great advantage, if more than one person working on a computer, you can merge more easily these than previously
It would have even the great advantage, if more than one person working on a computer, you can merge more easily these than previously.

Allow the users to make code reviews inside the file compare utility, so you can add your comments directly besides the changed code. Also send mail to the developer when a code review has been done and setup up some kind of workflow to allow the developer to rework it, give comments, and tell the reviewer to re-review it again... Also it should be possible to see that there are code review comments when checking out a file

Would like to see an all encompassing full featured and intuitive Web UI to replace the existing StarTeam clients.

Improve the message why some thing can't be accessed.
Currently the message box says: You have no rights. And thats it.

Which rights does StarTeam look for?
A more informative message (maybe hidden behind a bottom (more info) would be very welcome.

Label view allows multiple selection (version 16.0), but the freeze button is not clickable.

When merging files during a rebase or merge session, provide an option to specify a CR to which the resulting merged file will be linked

This is a bug introduced in newer versions of StarTeam. Previously, you could author your CR while popping over to an editor to examine code, documents, etc. and the page/cursor position in StarTeam would hold - now it resets to the top each time focus is removed from StarTeam - extremely annoying.

Currently there is no simple way to see which access rights are valid for a single file or folder.
You just see that there is nothing set at this file/folder.

How about show inherited rights as (non changeable gray text/items) in the mask?

So 'Advanced->Acces rights ...' would show the current state (black for set here and gray for inherited).
This would help a lot on finding problems, like I can't do this or that.

Are there certain filetypes that shouldn't be checked in against a certain CR? For example a CR that should not have sql files.

It'd be nice to be able to define these so that we could have an alert when a developer checks in a "bad" file. Let them do it but give an alert so that they can cancel.

I'd like a single "Commit change package" button within your GUI that automatically browses the working folder, automatically adding modified files, also easily allowing the user to tailor the change-package to include removed-files (ie, mark them as 'deleted'), new files (ie, mark them as 'Added'). Automatically detect if a file has been moved/renamed by comparing the checksums and mark such items as 'Moved' or 'Renamed'.

this would make the dev management process looks link smoothly.

Integrate Topics (Discussion) to other configuration Items:
-Like replacing the comments tab for a discussion tab and leaving the comment to a popup dialog that is shown olny when saving changes to the configuration item (specially change requests and tasks).

Ability to limit who can checkin changes at a folder level and at a branch view level.

The set of people may be different or a subset from the global set for a project.

So maintainers can checkin changes to a branch view but not into the development tip.

You may also want to restrict changes on a set of folders.

I think StarFlow GUI components should be extensions of CPC GUI components and no a alternative way of doing this. They should inherit their look and feel, icons and behavior.
In addition, they should be part of CPC, not something apart.