The new feature in 6.0 to relate test cases by dragging one onto another is great! Please expand this idea (or some other improvement) for establishing the relationship between requirements and test cases. Navigating the folder tree when using 'add' on the relationships tab is painful and the matrix report is not user friendly is you have too many results on the X or Y axis.

As a test manager I would like the ability to configure the screens for requirements, Test scripts, Script Assignments and Incidents so that I only see the fields that i need for the project and in the order that I is relevant to my project. This will allow me to only see fields that are relevant and are in use by my team.

As of today Users can only be added on LDAP synchronization.
Having the (pretty common and standard) functionality to remove users on LDAP synchronization would allow for much greater scalability of your product. (TMS-5026)

Every time you import a CSV via resources -> import, I need to remap every column and option, this takes a lot of time.

It would be great if you could save the mappings, with a name, and select the saved mappings when importing next time.

Also would be great if I could share my saved mappings with other people on my team.

This should include the ability to catch a change on the fly, make the update right then and there, updating all related scripts, then move on to the next script.

It would be great if it were possible to allow users to re-edit completed test scripts once they have been completed after an execution run? Often testers forget to add notes etc after they have completed a set of script execution runs. Unfortunately ET only shows a read-only view of the completed script after execution is complete.

Add called/linked tests capability - be able to call a test from another. The bulk copy allows you to copy steps that would be repeated but becomes a maintenance nightmare if those change - you have to change all tests then that have those steps instead of changing one called test.

The ability to set a Test Cases status to No Run after it has been placed into In Progress or any other final status would be great to solve a few issues:

If a tester accidentally clicks Save instead of Close on a test case the status changes to In Progress

If a Blocked test case becomes unblocked.

If a Failed or Completed test case needs to be rerun.

We have found that we very often reuse *same* Test Script in different scenarios (= assign it to different execution folders) . In this connection it would be very beneficial if each of these assigned scripts could carry their own unique names, while still subscribing to chances made to the mother test script (keeping her original name).
In other words, assigned "daughters" to any given mother test script should have the ability to carry their own names, but subscribe to changes made to their origin exactly as of today - i.e. except for a change to the mother name.

Currently it is not possible to add a new step or modify existing test step while executing a test case.
It would be good that such changes are allowed and when saving, then it would ask if changes need to be saved only to current run or update a master test case.
For executions which were started it would be good to have the possibility to refresh test steps from master test case. Now it will take changed test case only for the next run.

There are lots of charts, but no burn-down chart.

I would really like to be able to set the start and estimate end date for a cycle of testing (package), and track the progress over time over myself and other testers completing testing within that execution package.

I have setup dashboards for our projects, but users can not see them, and instead get their own copy of a dashboard.

To save users having to setup their own dashboards for each project, we would like the ability to create and share dashboards with other users.

Permissions are not at a granular level. eg it is not possible to allow a group/user to be able to add
scripts but not delete them.

Segregate the delete permission from Execution , Script and Requirement

Under Test management ' Manage Execution' gives even the delete permission to all users , same for Scripts and requirements . This will avoid deletion of folders by users mistakenly. Delete can be restricted to only 1 or 2 users from a project.

Users sometimes forget their ET password, and this requires an administrator to reset it for them.

I would like users to be able to request a password reset themselves if they forget their password, and to then receive a reset password email.

Currently it is possible to copy test steps within one test script, but sometimes steps repeat between different scripts and therefore it would be very beneficial to be able to copy steps across different test cases

We have a bunch of users who have left our organisation.

We want to prevent them from logging in, but don't want to delete the user, as they are part of our execution history.

Could you add a feature to disable a user, and not have that user show up in the user list or count towards our license.

We would like the ability to move the in-built fields into different places e.g. we want to be able to place some custom fields above the inbuilt fields, as we use them more often.