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.

The ability to filter entities (e.g. Issues) based on traceability to other issues (e.g. requirements or tests)

I want to add attachments to a step in the test run via the API. The attachment could be a screenshot or other helpful information.

This is already supported through the GUI but not the API.

enable to customize the graphs on the dashboard, and select what fields to see

we can link issues to tests and issues to requirements, but not issues to issues. that would be helpful.

tab that will show all the stuff that you need to do (Tests, Issues, Requirements, etc).

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.

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.

Add the ability to copy tests created in one project to another one

enable users to select how many Issues / Tests they want to see on each view

currently there is no possible way to attached pictures to a particular step

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 adding an attachment that is an image, display a small thumbnail of the image.

"Export to Xlsx" from filter should export test case steps and expected results

Exporting data from Practitest to Excel is a powerful feature. But it the data that is exported is limited. In particular, the traceability information would be a very useful addition.

The REST API lets us create requirements with mappings to test ids. The typical use case is for requirements to be defined and then QA dev creates the associated test cases. The user interface allows the workflow, but the REST API does not.

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.