Since a while now we use a combination of Confluence (overview, reports, manuals) and plain Jira (per case/topic one issue).
Imo this open/passed/failed… ratio isn’t worth a thing. Just create tickets for testing on regular releases.
You can do test (case) management with very simple, already existing things.
Reports should not be about pure number, but about coverage by topics, risk and relevant details. That is something you have to write, not to count.
For new features we use mostly Jira. I do most of my test planning & reports in the original tickets. Either in the descriptions or in the comments, depends on. I have no scripts.
I exclude (and link) some things to Confluence, partly because the Jira issue description isn’t save for parallel editing.
At least I have no “do X, checkY” in Confluence for new features.
This is an approach how to use only Confluence (I guess many other wikis would do it) I’d love to try one day:
I should make this a blog article which I can link. I keep repeating myself similar to the questions.