Feature Requests

Right now I can link individual test cases to a Jira ticket, but it would be nice if I could link a whole suite to a Ticket so that I can run multiple tests more easily

Requirement: I want to link new/existing JIRA defects in the test runs Currently this is not possible in qase & in some way the report looks incomplete. It would be super helpful if we can see JIRA defects in the test runs as well as in the reports.

The Qase plugin does not support dark mode, meaning any Qase view is stark white against the dark background of Jira when in dark mode.

When I moved a set of Jira tickets from one Jira project to another, the Qase integration test case linking was lost. The newly moved Jira tickets no longer had any Qase test cases linked to them.

[Qase] Open test case [Qase] Click "Link Jira cloud issues" [Jira] Copy jira link by icon click (see attachment 1) [Qase] Paste copied jira link and click "Search" button Actual result: No results has been found (see attachment 2) Expected result: jira task is found by full link

Now it is possible to connect only one slack channel with notifications from Qase, but we have huge amount of projects and it is difficult to read about all projects in one chat. That is why it would be nice to have possibility to send messages about changes to different chats.

Create Test run Click "External issue" and select Gitlab integration Fact: drop-down list is so tight, I can't see list of projects normally Expected result: drop-down list's width is amount 1/3 of search field approximately

Right now we can only attach GitHub to defects created in Test Runs, we'd like to be able to link them to Test Cases or Test Runs like with Trello and Azure

We are using the jira integration to be able to create jira issues linked to defects. In a certain case, we discovered a 'ping-pong' behavior, where a jira status change triggers a qase status change, which in its turn changes the jira status again. E.g. we set our jira issue from "IN QA/Testing" to "Deployed to stg". This in turn sets the linked Qase defect to "Resolved" (Which is okay. It is not ideal for us, as "deployed to stg is not the final state", but I know we cannot change the status mappings as for now). However, this change in the qase defect in its turn sets the issue in jira back to "QA completed". In my opinion this second change shouldn't happen. The status change in Qase was triggered by jira, so it shouldn't trigger anything back in jira (which is kind of a ping-pong effect) As a side-effect, we miss those issues in jira when we filter on status "deployed to stg", causing us to forget testing those.

When we put a jira issue linked to a qase defect to 'Rejected' (which is an end state), we would like the qase defect to be set to 'Invalid' instead of 'Resolved'.