When we open new bug using Manual Testing page, we have to do two steps. Firstly open the bug then assign. We want to adding "assign to" field into this page to choose developer in the first step.

Please add a checkbox to run tests with status N/V (N/A in english?)

http://documentation.microfocus.com/help/topic/com.microfocus.sctm.doc/SCTM-2CE89FAC-RUNDIALOGBOX-REF.html

At the moment I can only run tests with status failed. If I add a new test to the plan it can not be executed. I have to run the complete plan again.

A listbox where I can (un)select tests would also help me a lot.

When exporting a test tree into excel, if a test attribute is set at test level, it is shown in excel, if it is set at parent folder level (i.e. inherited), then it is not shown in excel. It is not understandable from an end user point of view not to see his test attributes in the exported file because they were inherited from parents folders.

We would like to import old test results that have been created without SCTM in order to create reports with historical statistics inside of SCTM.

During the import of the old test results SCTM should:
* create unknown test cases automatically.
* create one new execution plan that is linked to all executed test cases

It should be possible to set a planned execution date and time for every test case in a test cycle, to enable the comparation between planned and actual execution times.

Implement via API or Web Service to 'External Assign Issue' function so that it is possible to pool
Issue new within Starteam to Silk.

Problem: Inside the Silk can associate Issue a Change Request, but the Change Request is not possible to associate
Issue one.

Please modify the current mechanism in Silk Central Test Manager so we can recover removed execution plans. We have accidents that the users accidentally made execution plans removed due to the removal of underlying tests and test containers and we have no way to recover them.

Lors de l'exécution manuelle d'un test, je souhaite déclarer un incident donc je le créé pendant le RUN.
Serait-il possible de récupérer automatiquement le Produit + Version + Build sur les quels se déroule le test.

In configuration suite we can create plans and assign people to them directly.
So will be good to import execution plan to Test Cycle directly to selected user, not to "unassigned" list. Without drag-n-drop, etc.

Have an option within the Requirements > Document View to only return the leaf nodes of the requirement tree

When using the output.xml file to input values in the 'Timeline' tab, we need to have the ability to render URLs as hyperlinks, either through XML tags or automatically.

This is a continued issue from Incident #2667867

Export / Import SCIM project with option to work linked to SCTM project export/import capability.
In some case we have the need to 'move' a SCTM project form a DB to another including the defect linked into SCIM project. To do that we need to have the import / export capability also for the SCIM Issue Manager project, working linked to SCTM project (test - defect associations).
thanks

A filter is used in the test specification document view so the display is not adjusted/tailored for Status values and assigned test specifications.

We need a standardisation of the display in the requirements and execution areas.

In the case of refactoring/redesign, there is no easy way to export test plan information AT THE GUI level and re-import these to a newer structure.

Also, another Use case here is take assigned tests from an Finished Test Cycle and add these to a new Exec Plan by using an export feature.

Provide a way to deactivate the email notification when a user is assigned to tests of a test cycle

I have created the subscription for several custom reports I made and added them to my dashboard but they just show the data and not the chart view. Is there any way to see the chart view on the dashboard instead of the data.

Selectable TEST and STEP ATTRIBUTES visible on manual test execution interface SCTM after v12.0.
In some cases the step attrubutes are used to drive the test / step execution, as yet used in version 12.0 for step attributes, visible into the web manual test execution interface.
Gianni

At the moment the results categorization for simple reports is too restrictive. It should be expanded to allow such reports as Test IDs per requirement name.

In 15.5, the number of integrations possible to define for JIRA Agile was increased to 5.
However, this is not enough. We need more since our projects in SilkCentral span more projects in JIRA. This is also related to the need for a concept of "product stack" or similar with the ability to define tests and execution plans/cycles that span multiple products.