Feature Requests

Right now the custom fields are ordered in chronologically from time of creation, we want to be able to set the order as we want, maybe even at the Project level if possible, if not in the https://app.qase.io/workspace/fields

With the ability to set parameters on a test case it'd be nice to store those paramenter entries as variables and have them entered in a test case like a variable {{$sorting_parameter}}. And eventually at test runs instead of having those params shown only before the steps - we could fetch the parameter value and put it into the step.

For lengthier test cases, knowing where a given test case has failed in previous executions in terms of its failed test steps could be helpful for several reasons, including the identification of particularly sensitive areas of code regarding the introduction of regression bugs.

As a Qase user I'd like the ability to add comments on the test run as a whole- so that if I need to call out specific details, issues, or other notes on the run as a whole I can and it will show on my Qase shared report as well. Given a test run is finished When I select "Complete" Then i am prompted with a Run Comments/Notes section where I can input notes and/or add attachments

Feature Request: Introduce an archiving feature to manage unused test cases while preserving their full history and metadata without inflating repository size or losing change records. Problems now: • No efficient archiving: Current options require either moving test cases to a new suite (which increases repository size) or cloning them to a separate archive project (which doesn’t preserve their change history). • Can't delete them because: The trash bin lacks filtering and viewing options, making it hard to recover or manage deleted test cases. Proposed Solutions: Labeling for Archival Management: • Enable users to label TCs with tags like “Archived,” “Trash,” or other custom names, organizing inactive TCs within the same project. Improve Trash Bin options: • Add filtering and search functions in the trash bin to help locate deleted TCs. • Enable viewing of TC content directly within the trash bin to support informed recovery decisions. Flexible Clone and Restore Options: • Provide an option to transfer TCs between projects without losing their history. Why this is important: As projects evolve, archiving is essential to manage TCs effectively without losing valuable data or cluttering the repository.

In the repository, having 10 test cases with 3 parameters in each would obviously be 30 test cases which need to be run (in our case, manually). It would be great to see that 30 figure perhaps bracketed when looking at a repository along side the Cases/Suite figures. It would help when trying to estimate how long testing will take prior to building a test plan/test run. Example: Selected: 10 cases (30) | 2 suites

Update the "Test Runs" page frequently (with e.g. WebSockets) so that it doesn't need to be manually refreshed in order to get the latest test run results.

It is very difficult to see the reviewer's comments when you are updating the test case. You have to edit in another tab to be able to see the comments. Taking this a bit further it would be nice to comment directly on the area we want adjusted rather than having comments on the side.

As user, i want to discuss with my colleagues about test runs before testing, or make change, etc...

The reporting for automated executions should be more robust. Allure is an example of how this can be done - with nested steps, attachments, stack traces, variety of information to view consume and analyze.