Qase Roadmap

Currently, the public API only supports linking/delinking Jira issues to test cases in Qase. There is no option to associate issues from other platforms such as Linear, ClickUp, GitHub, or others via the API. Adding the feature to link/delink issues from other platforms through the API, would be helpful.

In the testrun screen only the actual numbers of testcases are shown in the different status. It would be great to also so the completion % here in this screen, so you dont need to open the testrun to see this. Currently doing UAT test with several users, so if i want the % I need to open each test run to see it

When creating a Test Plan with test cases from different folders in the repository, if we want to have them arranged in a happy path, we will have to create a folder specifically for that purpose (having even to clone the existing test cases if we want to keep them in their original location while adding them in a specific position for that Test Plan). Having the possibility to arrange the test cases inside a Test Plan without altering the folder structure of the repository, would be very helpful, avoiding duplication and extra work in those cases.

As a QA, I want to pass tags from code in fields() automatically. Example: .fields({ severity: 'blocker', priority: 'high', behavior: 'positive', layer: 'e2e', tags: ['example tag', 'tag2']

Currently, 1 failed test causes the entire run to be Failed. It would be good if a % acceptance threshold could be set for a given Test Plan (e.g. 95% for regression). I realize you can do Mute for tests but the option in the tets plan settings adds more flexibility

It would be nice to have a name field for cloned test case, not only prefix which is added to inherited test case

In 'Edit Run' view theres a 'Select cases' option which allow to added more cases to the run. It would be nice if this view was a general test cases view which allows not only to add but also remove test cases.

If we have a large number of test suites in the project, during various operations (cloning, searching) after selecting a specific suite from the list, it is difficult to find the location of this suite after expanding the list again. Example for cloning test cases - after selecting suite, when i try to selct again, the list is going to the beginning not for current location of selected suite:

Shared steps are very useful and i propose will be a lot more if we could parameterize them. For a piece of data thats required in the shared step can be named as a variable/parameter which can be specified a value either in the test case or during test run time. This will make the shared steps way more reusable and us QA Engineers a lot more productive.

Today users get easily confused when cloning test cases, causing them to clone the test case along with the suite which is a hassle.