Our objective is to connect Silk Central test manager platform on our corporate LDAP Directory which is based on the product ‘sun directory server directory 6.3’ (known nowadays as Oracle Directory Server 11g).
The LDAP directory enhance the password policy which force password expiration every 90 days and blocks accounts after several failed attempts.

SCTM v 13.0 doesn’t handle the error messages sent by the LDAP Directory when the password has expired or when the account is locked and therefore the user doesn’t get the reason why the authentication has failed ( “Vous avez entré un nom d'utilisateur ou un mot de passe invalide.”)

We would like an evolution of SCTM which will handles these specific error codes and print specific error message to the end user as specified as below :

Error code : Constraint violation (19)
Error detail : Exceed password retry limit. Account locked.
Message to expose to end-user : "Blocage temporaire : votre compte a été temporairement bloqué pour des raisons de sécurité. Merci de réessayer dans quelques minutes."

Error code : Invalid Credentials (49)
Error detail : Password Expired !
Message to expose to end-user : "Votre mot de passe a expiré. Merci de le modifier en cliquant sur le lien ci-dessous.*"

The deletion of an Execution Plan / Manual Test Cycle will produce the deletion of all the the test history result.
This condition is not acceptable, the test history is an asset of the test factory organization while the execution plan / test cycle is how you organize the work daily with your testers.
This condition is improved also by other conditions:
1. the number of test cycles will grow very quickly, due the fact that you have to recreate (correctly) new test Cyle for each new run (if you use the standard EP you can rerun the same EP).
2.You haven't any manual testing cycle manageemnt capabilities, to hide or sort/repositioning the created manual test cycle in the SCTM section.

The test result history should be indipendent from EP/ Test Cycle.

Thanks

Giovanni Pistarini

The missing capabilities in Manual testing Cycle are:
1)No list/sort capability of Testing cycle
2)No immediate evidence of started and to be start Testing Cycle
3)No possibility to manual repositioning in the pane
4)No possibility to hide testing cycle
5)No possibili to compact testing cycle
6)No possibility to preassing build to testing cycle

The not acceptable capabilities are:
7)No warning message that deleting the testing cycle
you will lost all the result data
8)No possibilty to archive the test result indipendently from testing cycle
9)No possibility to use the DashBoard "... Result Summary" and "... Cycle Progress" without use the testing cycle

So, our SCTM implementation plan is to end the pilot projects in August and extend SCTM across all the Poste Italiane Projects (more than 500/year), defining the guidelinees to use it and starting from September / October
Following this plan in 2/3 months of activity the MANUAL EXECUTION PLANNING will come unusable here, so I have to decide into August how to use SCTM and I need confirm if something will be changed in next release (Nov2012).

Remove default risk and priority requirement properties while the default lists of values of those ones don’t fit the customer needs. Creating custom risk and priority properties introduce confusion for users.

About this issue, our customer would like to be able to define their own list of values (different values and different number of values than the standard lists) for the standard requirement properties Risk and Priority in SCTM 12.0.
So they create custom requirement properties.
However, doing so, they get 2 priority and risk properties on SCTM UI in the requirement workspace, the standard properties and the newly created custom ones.
So they would like to be able to hide the standard properties that will not use anymore.
This is creating some confusion for the users on SCTM UI.

Much like the Atlassian Greenhopper integration fetches relevant information about requirements from JIRA and presents them in SCTM, it would be really useful to have a JIRA plugin that does the same thing but the other way around.
For an epic, story, or a defect, the plugin should present information about relevant tests for this epic/story/issue.

The use case would be to allow for users of the issue tracker to view test related information in the context of the issue.

Information to be shown would be all relevant information about a test case/execution plan, test results, status etc.

Most competitors to Borland offer this, and it would be an example of acknowledging the fact that for a development organization, the single point of truth lies within the issue tracker.

We would like to allow certain users access to only certain projects in Silk Central. I know we can create Groups and allow members of that group access to only certain projects but we were wondering if there is a way to do this without the use of groups?

For example, it would be nice if there were a "Projects" drop-down list in the "Groups and Role Assignments" section of the User's Profile page. So that we could select specific projects for a specific user. The reason we would like to this is to avoid having to create dozens of new groups for specific projects.

-from case 2602990