Feature Requests

When selecting multiple cases at once in the Test Repository, it would be extremely helpful to have an option appear that says "Add to Test Plan." Especially in larger Test Repositories, it reduces the need for the user to keep track of where each individual case lives after creation given that they could be added at the time of creation. The actual functionality could be implemented in a similar way to how you allow searching by External Issues (select "Add Test Plan," then select a preexisting plan from a dropdown, or allow for the creation of a new plan from this menu).

No way to see from the list, need to be able to see plans for each Suite/Case. Would be beneficial when testing only parts of a project which has changed. Would allow for more organization when testing.

Hi there, There is an option to share test run report via PDF but it does not include Description of the test case. When sharing with clients, description is requires. It will be great if you can add that feature soon. Also, it will be great if there is a desktop software for Qase. It will be easy to work on for daily users.

If a run consists of many suites, it's hard to navigate around it, since there is no condensed suite tree (similar to the one in repository), and there is no way to navigate quickly to a specific section without lots of scrolling.

On an existing test run, it would be very helpful to have the ability to select a test plan. The test plan drop down is only available when creating a new test run. By selecting a test plan, the test cases in the test run would update with the selected test plan's test cases.

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

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.

When any Test Run is exported, linked JIRA ticket id should also be exported

When bugs were created directly in Jira and we just want to link them to failed test cases, we are unable to do so.