Keep in mind:
- a lot of data isn’t within Nextcloud Server but in the surrounding infrastructure (web server and reverse proxy; not to mention the web browser console, client installations, etc.).
- the script has to be independent of Nextcloud Server since by definition the Server installation may be offline/not functioning properly (so a Nextcloud app is of limited use)
And none of these questions on the support template can be answered by a script:
- Is this the first time you’ve seen this error? (Yes / No):
- When did this problem seem to first start?
- Installation method (e.g. AIO, NCP, Bare Metal/Archive, etc.)
- Are you using Cloudflare, mod_security, or similar? (Yes / No)
Summary of the issue you are facing:
[…]
Steps to replicate it (hint: details matter!):
[…]
Log entries:
Nextcloud Log - Please provide the log entries from your Nextcloud log that are generated during the time of problem
Web Browser Log
Web server/reverse proxy Log
That’s most of the template.
Additionally, the support template itself is a useful troubleshooting tool in itself:
- if one wants to try to troubleshoot a problem in their environment, the template asks for the things that need to be looked at by someone troubleshooting (such as the person posting themselves)
- if the poster (admin of an installation) isn’t able to to readily figure out how to check their various logs, it’s not surprising they haven’t solved the problem on their own. And it’s probable that learning that is a good starting point[1] since it’s unavoidable even if they’re seeking assistance from others to analyze the logs (particularly initially).
Also let’s be real here: Nextcloud Server is not a consumer app. It’s an enterprise app. There’s always going to be a fair degree of technical knowledge and local deployment environment knowledge expected of the operator.
Not saying they’re can’t be some incremental improvements, but I’m not sold. 
Don’t get me wrong: I’m not discouraging experimentation and brainstorming. I’m just trying to point out that there are people around that have put thought into a lot of this. And the above are some of the challenges I’ve noted in my own journey down this path.
Footnotes:
[1] This itself might suggest a compelling reason to add links to specific key bits of documentation in the forum main menu header. Basically quick links in the header for 2-5 of the most essential troubleshooting/day-to-day admin processes. Ideas:
- Official Documentation (e.g. Nextcloud Server Admin Manual)
- “Where to find your logs?” [examples for all major deployment methods]
- “How to run
occ?” [examples for all major deployment methods] - “Quick Start Guide / Model Base Deployments” [examples for all major deployment methods with a narrowly defined scope]
(all of these bits are around but spread out).