QOL Features Zephyr Scale is missing

Question

Our company pivotted to Zephyr Scale about a year ago, having previously used Test Rail.
I liked its deeper integration with Jira and ability to add custom fields.

However there's now a number of glaring QOL issues I'm really getting sick of struggling with.
Notably.

No dark mode - this should come as standard on software now-a-days.

No ability to filter test-cases by Folder - notably you can't filter the ones NOT in a folder - this is amazingly frustrating as when someone creates a case and forgets to add it to a pre-made folder it's lost like a needle in a needle-stack.

Reporting is incredibly limited - notably it doesn't give any information on test cycles, I can't seem to get the default reporter to produce a matrix that gives test cases in a cycle, and then what jira tickets that cycle covers - this seems like easy functionality for when you're dealing with.

Cannot later add executions to a test cycle - if I run a test case against an individual jira ticket that execution can't then later be added to a cycle, giving an uneven/wonky representation of the testing that has gone against said ticket.

I'm sure the API allows for more granular control, but as it stands I'm starting to think about pivotting away from Zephyr Scale due to these limitations, instead moving to a better tool.

AI automation is cool and all, but these are some basics I'd have expected Smartbear to cover.

misterb · Answer

I have similar frustrations - there are some easy fixes that would greatly improve my QOL using Scale, I wait and hope for these to be addressed.&nbsp; But to try and help you with your issues...
1. No ability to filter tests that are NOT in a folder: you may be pleased to hear that this is actually possible - see image below for the option to enable/disable this view.

&nbsp;
&nbsp;
&nbsp;
&nbsp;
&nbsp;
&nbsp;
There is no matrix to produce Test Cycle and a list of issues, but depending how important it is and how much effort you want to spend, you can find/list issues individually by Cycle:

Add the Issues column to your Cycles page view
Hover your mouse over the number in the Issues column
Click the link to view in Navigator and Copy the issues from that list

Another alternative is to export all test results and use Excel to get the information you need - I have to do this myself to plug the holes in reporting, e.g. production of a functional Burn chart.

&nbsp;
&nbsp;

ed_h · Answer

Agreed ; Zephyr managed to clear the incredibly low bar of Testrail, but running headfirst into it's incredibly limited API and functionality, plus the largely dead community and lack of visible development support makes me think that the search for an integrated jira solution might lay elsewhere.