thank you for reply, @clittlefair !
I am familiar with Qase and Testmo. We’ll definitely will be evaluating them. Will have a look at 2 other suggestions.
What I liked about Testmo is an ability work with 3 test types: automated, manual, exploratory.
I agree XRay is expensive as it is based on Jira users count.
The most important factor for us is probably USABILITY and LEARNABILITY.
Of course, we also need integration with Jira.
We’ll get there 
Thank you.
Looks interesting.
If the primary driver is external visibility and reporting rather than building a heavy internal process, I would bias very strongly toward something lightweight and fast to stand up. I have been through this exact situation twice now, and the biggest mistake I saw was over buying for features that never actually got used.
For your specific needs, pulling automation results, tracking exploratory work, pushing to Jira, and producing clean charts, tools like TestRail, Qase, and Tuskr all technically cover the basics. Where I saw the biggest practical difference was friction. TestRail gave us powerful reporting but at the cost of constant admin overhead. Qase felt modern but we still ran into performance issues once the suite grew. We eventually settled on Tuskr because it hit a good balance of being simple for the team while still producing the kind of dashboards leadership and auditors wanted. The setup was measured in days, not months, and linking runs back to Jira was straightforward. More importantly, it did not actively get in the way of actual testing.
One piece of advice regardless of tool: define upfront what metrics you truly want to show externally. Execution coverage, pass rates over time, regression signal, and traceability to Jira are usually enough. If a vendor demo starts drifting into dozens of vanity charts, that is often where the six month disappointment begins.