Feature Requests

This widget can take a numeric or text value from custom fields, or from something like “Project Variables” if you add support for storing additional information. If the value is numeric, it displays the average value, depending on how many projects are selected. If only one project is selected, it displays that project's value. You can also choose a table, pie, or bar representation by project. If the value is text, it displays the text inside the widget. If multiple projects are selected, the values are shown in a table view. ... We need this feature because we want to place the unit-test coverage percentage into this widget.

Could Qase support to highlight the differences between texts before and after when updating cases? It's not easy and intuitive for reviewer to see what's the differences.

I would like to request the option to mark the attachments section in defects as a required field. This would help ensure that users always upload the necessary attachments when submitting defects in Qase.

Currently, Aiden’s manual test case generation only uses the Jira issue “Description” field as input. This means important requirements stored in Jira custom fields are ignored during test generation. As a result, users must manually copy data from custom fields and other details into the requirement in Jira issue so that AI take it into consideration when creating test cases.

There should be a way to submit test cases for mass review. Either by import, by API, or by selecting all test cases. Currently we have to submit for review one test case at a time. This takes up a lot of time.

I would like to get all requirements for a project like this client request does: https://app.qase.io/v1/requirement/tree , and a way to get individual requirements

Now the "Send to review" button can only be found when I go into the full case edit page which is very inconvenient to use when I have multiple cases need to modify and send for review. Add "Send to review" button beside Save button when editing case from repository list will improve the efficiency a lot.

Currently it's not possible to set an order of Test Cases inside the Run (by default order is by ID). But sometimes it's crucial to have a specific order to execute run in a more effective way.

We currently cannot use the Qase automation. tooling to test our app because we require OAuth login flows through Google or Microsoft. Your tool does not allow this and as such we have to find other options. Could you add support for driving the browser through Google and Microsoft OAuth flows?

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