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.

The current notification agent is a 32bit agent that runs against the workflow. But with our setup which has hundreds of projects and possibly thousands of views, we are not able to run the agent on all our projects due to memory issues. It would be nice to see the notification agent completely integrated into the ST Server.

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

Add a feature to introduce project consolidation tooling.

STCMD CO switch to pass in a list of CRs. It should checkout the latest revision of any file linked to one or more CRs multiple times. An optional parameter to have Starteam generate a rev label to attach to the CRs and Files.

Create a integrate User Management System that enables centralized user management for Caliber, StarTeam and SilkCentral.
In addition, it would be nice that it could manage Belise license distribution/association.
And that it replaced StarTeam LDAP QuickStart Manager.
In addition, it would be nice if it´s interface were web based.

Before the start of a vcm commit, vcm should check to see if any files(items) participating in the session commit have already been changed

this would make the dev management process looks link smoothly.

Migration of discussion items from Knowledge base to Community, missing many attachements. It needs to be fixed promptly...

For "shared resources" who could potentially be working on multiple projects at any point in time, it would be really useful to have a personalised dashboard on the Home/Welcome page, which gives a high level overview/list of all tasks currently assigned to that user irrespective of project and sprint.

When there is a block of lines that are different (new, deleted, modified, etc.) in the File Compare Tool, the Delete, Replace, and Append text buttons will do that option for the entire block that is different. It would be nice if you could highlight a subset of those lines and then have the action button apply this to only those highlighted lines. (If nothing highlighted, then action would be as today.)

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

As it right now Agile works well enough to plan a sprint by assigning story points and determining which stories can be accomplished. However, the ability of the developers to change the story point estimates and task estimates makes it difficult to figure out how well the team is doing against their estimate. It would be good to be able to save a baseline at the beginning of the sprint.

In the File Compare Merge tool, the area between the scroll bar and the window frame shows an overview of the comparison results. However, the area is too narrow and the colors are too light (too washed out) to make the feature very useful. Please widen the area and either darken the colors or darken the background to increase contrast.

Additionally, I'd also like to be able to click on the colors to go directly to the related change.

Both of these are similar to how Eclipse handles Annotations in the Overview Ruler of an edit, for example.

This is more of an SDK+server related request. It'd be nice to know who modifies view properties (eg, the view description, or the view gets renamed/deleted). The ViewEvent - viewChanged() method seems to trigger nicely on such changes, but contains no information regarding who did that change. Could such information be provided in future server+sdk releases?

A related forum post can be found here:

http://community.microfocus.com/borland/managetrack/starteam/f/60/p/10747/17040.aspx#17040

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.

Allow entry of fractions in the task time sheet without a leading 0 (e.g. making the entry .3 a valid entry)

When a script is ran, I'd like to be able create checks that output results as Pass, Fail, or Warning. The "Warning" option allows me to prioritize viewing results. If the script outputs Failure, then it is something I have to review immediately. But if I can output warnings, then I'll be able to prioritize and review when time permits.