Testset that contains several existing testsets
what do you think?

When exporting a view, especially one of issues. The ability to sort by a particular column does not exist. This feature would give stakeholders the ability to generate reports. For example, export all open bugs sorted by priority.

Currently there is no way to select multiple test instances in a set and mark them as passed/failed or blocked. We suggest adding this option to save time in case the tester know that several tests can be modified accordingly. This will save a lot of time and effort of clicking.

Currently, by cloning a test, the
Author is copied from the original test.
This may cause confusion when users clone tests and modify them.
Setting the cloner as the Cloned Tests' Author will solve this issue.

Add ability to create test sets straight from the test library using the mufti selection check boxes

...It will be very useful and will save time

Add Test directly from a Requirement and link them for traceability at the same time. When we create our tests they are based on the content of particular requirements so it would provide a much faster way to develop test coverage and prevent from have to search to associate them together afterwards.

The option selected in the drop down controlling the number of issues displayed per page is not persisted. If you change the option, view an issue, then return to the "Issues" tab, it is reset to 20 issues per page.

When test status is changed from "Draft" to "To Repair" or "Obsolete" a comment should be attached explaining for the reason.

enable an advance search, where we can set each field, whether it's a custom field or a system field.

Create a New Test directly into the folder highlighted/selected. when creating a new test I currently, regardless of folder selected on Test Library tab, have to manually set the 'Test Folder' as part of the test creation. Otherwise the test is created in the root folder - terribly inefficient.

e.g. I have created one Custom View as 'View1' which has several child custom views such as 'View1.1','View1.2'. Now i create another custom view below 'View 1' as 'View 2'. Having the ability of simply copying 'View1.1' and 'View1.2' under 'View 2' would save lot of efforts for users. Especially if you see your project having number of similar tasks being created under it repeatedly.

In addition to "time/effort" field (Asked by Kylie) please add the following graph:
X axe will represent the SUM of the Time/Effort , Y axe will represent the instance run status in order to estimate how much TIME left to end of cycle and not only how MANY tests left.

It would be a great benefit to us if the filter coould be like it is in excel where you have the poosibility to customize it so you can define your own filter. For instance fileter on several "status", not only one.

It would be good if the table cell or text for the requirement status is colour coded to make it easy to identify requirements which are not covered, not ran etc.

For example we have a view with a lot of child views and now We would like to create the same view but with a different parent filter. So we would like to clone the existing tree and modify it instead of creating it from scratch.

Add ability to convert a search to a filter (which can be later customized).

Linking external id (Requirement id) to test library and instances