Feature Requests

To give you more context of my flow: I create a set of new test cases These test cases have a custom field called "Project status" which by default has "Planned" I add these new test cases to a new test plan A few weeks later the project is ready for QA I executed the test plan and everything is green The project is delivered At this stage, I would like to update the "Project status" field to "Implemented" in bulk only for the test cases inside the test plan. Unfortunately at the moment I can't do this in bulk, but one by one. If the test plan has only 10-15 test cases it's rather fast, but if it contains 50 test cases, it's quite of a headache.

When there are open reviews that await decision, it would be useful to see a badge with the number of open reviews next to "Review" section - see screenshot.

I wish I could filter inside my repository based on one or more specific test plans.

Our automation team uses the Qase v2 API for uploading bulk test results at the end of an automation test run. It would be nice to be able to include the tags we have on our Cucumber tests in the API request to be synced to Qase. As an example, the following JSON would set the Tags on the the Qase Test Case to "Bugged" and "Login". { "execution": { "status": "passed" }, "fields": { "tags": [ "Bugged", "Login" ] }, ... } This would be helpful for us to have an additional way to filter on test cases.

Problem: Currently, there is no straightforward way to create a new test run that includes only the failed test cases from a previous run. While there is a filter available on the test results page, it doesn’t apply when selecting the “Run again” option on the test run page. This limitation makes it difficult to repeat tests for only failed cases in an efficient manner. Users need to manually select failed test cases and set up a completely new run, which is time-consuming and prone to error. A feature to directly create a new test run with only failed cases would streamline the retesting process and improve workflow efficiency. Attaching a screenshot from another TMS w/ this option, for comparison:

Please add or extend APIs to support retrieving "assignee" for cases in TestRun. I want to use it in our custom application.

It is required to add test case preconditions to the test results report PDF.

When a review request has been completed (approved or declined, but closed anyway), the comment box still appears in the request as if the comments are allowed. However, when one attempts to send a comment, they would get a toast with the error (see screenshot). It would be a more intuitive experience, if the comment box was removed or disabled for the completed reviews in the first place, instead of allowing the user to input the comment - to only find out they cannot send a comment.

I've noticed that when writing a test case, if the page reloads for any reason, all progress is lost unless each step is saved individually. This has caused me to lose work multiple times, wasting valuable time. Often, my computer restarts on its own, or the page reloads likely due to a release on your side causing my browser to refresh without me realising. In all these cases, I’ve lost unsaved test cases because I hadn't yet completed them. Jira has a feature that prevents data loss for unsaved work, allowing me to retain my testing progress. I’d love for this to be implemented, as I know it’s not a complex change. Given the cost of using this application, adding this feature would make it much more worthwhile and help justify continuing to use it rather than switching to an alternative. I attach an image so you can see what I'm talking about. Thanks, Andrea

In case reviews it's not clear where an adjustment is made. Solution: Highlight the step with the adjustment.