Feature Requests

Hi Team, We have a project setup that includes multiple microservices, each organized under separate test suites within a single Qase project. Currently, the dashboard provides an overview only at the project level, which makes it difficult to track the health and status of each microservice independently. While creating separate projects for each microservice is an option, this would lead to significant test duplication and overhead in management. Feature Request: We would like to request the ability to filter the dashboard view at the suite level within a project, so we can monitor progress and execution results more effectively for each microservice without needing to split them into separate projects. This enhancement would improve visibility and maintainability for teams working on microservices architecture under a unified test project. Looking forward to your consideration.

Currently, Qase offers an issue tracking integration for Azure DevOps, which is great for linking issues and test cases. However, it would be incredibly valuable to have native CI/CD integration support for Azure DevOps as well. This would allow teams using Azure Pipelines to: Automatically trigger test runs on Qase as part of their build/release pipelines Push test results to Qase directly from Azure DevOps pipelines Seamlessly track test results as part of their CI/CD process without relying on custom scripts or external tools

Currently, when filtering test cases for specific parameter values, an 'OR' logic is employed. Meaning, if three different param values are selected, it should fitler for all test cases that have ANY of these values. In some situations, for a more focused filteration, an 'AND' logic where filtering for cases that contain ALL of the params would be more helpful.

I want see the exact cases numbers (with links?), not just the total number

Add the ability to save parameter/values as "shared" so that they can be selected for multiple test cases.

Require ability to export requirements in excel and PDF

When working on a Test Run with Wizard opened, interacting with “Submit result” button may require closing or resizing the side panel in order to change the result of several test cases at a time. Potential solutions: Change the orders of buttons by moving “Submit result” all the way to the left next to "Assign". Buttons could adjust their positions depending on the size of the side panel to always stay visible.

Currently Filtering via Tags is only supported in Repository and Test Run views, but when expanding the test run to view test cases, users are not able to use tags as filters in there Adding this would really help in the process of selecting specific test cases for execution

Add the ability to separately configure each project to send messages to different workspaces in Slack