There are no pages in PT that actually remember the width of columns or sorts. This makes using PT pretty annoying for people who manage or run test sets, issues, or requirements.

Currently I can import the requirements (eg: 1,2,3) and the tests (eg: 101, 102,103) but I cannot import the links between the two and need to link them manually. I'd like to be able to import the mappings by creating a csv file.
eg:
Req, Test
1, 101
2, 102
3, 103

Currently, when you enter an existing test set, the Test Instance Name column is very narrow, cutting off most text of the test name. I constantly have to increase the Test Instance Name column EVERY time I reload the test set page. It's very annoying. At the very least, it would be nice if the column width would be remembered while I'm actively so I don't have to constantly increase it.

It would be nice if there was a way to include photos and attachments that are included in test in the final report for reference. It can be odd at times to have a test that references a picture or attachment and it does not show up in the report.

Creating an issue in JIRA should take more than 1000 characters(This should include all steps from test Set in PractiTest)

Would like to have a single dashboard that can cover multiple projects. As a manager of projects this would be highly benefitcial.

Create possibility of adding parameterized values to test cases or steps and generation of new cases from predefined csv lists with values for these parameters. FYI This feature exist in QAComplete :)

I have a field "Product Area" that I set for the TestSet. In Dashboards reports though, I don't get much value from showing the Product Area by TestSet, I want to see it by Instance.
Having my testers to set this field again and again for every test instance is an unnecessary overhead.

We can already see that information through the Traceabilty, but currently I think that It's not possible to create a filter in order to get all the tests linked to a specific/s Requirement/s (for example, in order to create Test Sets for specifics requirements).

We need to create an extra field with a list of requirements (manually added), when this information already exists and we have duplicate information.

I think that the creation of tests by requirements is a very common way of work, and it's not easy to get right now.

Thanks.

in the same mechanize as add test to a test set, instead of picking them one by one like today

When I am in the Tree View in Requirements and add a child to an existing parent then save, my focus returns to a strange random spot in the tree and I have to navigate back to where I was. Some are expanded and others collapsed. It would be nice if focus would return without having to collapse other entries that were not even accessed during the session.