Tired of trying to understand feedback, no problem, create a issue template so the meaning is clean and clear to understand for your team, well yes and no, I actually wanted the form version which I have been seeing on public repos but thats not yet available on private repos. π¦
How?
Settings and Issues and then setup templates or just dump out the md files to .github/ISSUE_TEMPLATE dir but the first way is cool too.

I created three types now, ideas for all my thinkings.

Now when I log my idea, at least some settings are pre-configured.

Its still not as cool as the form templates on public repos but you can follow that beta program here, GitHub Issues Forms Template for Private Repos.
Looking forward to that.. π€©
Conclusion π
Conclusion monkey says its easy for devs and non-devs, itβs enough for me to work with, will be doing PR templates and config.yml for defaulting, and maybe a action to assign each new idea to a project board nerd hat on. My brother will love that.