We do already have this page, on the website, about writing bug reports:  https://inkscape.org/en/contribute/report-bugs/.  I helped with writing that, mostly just changing language so that less technically-oriented users could use and understand it better.  I'm sure it could use further improvements.

When you click on Help menu > Report a bug, that's the page that opens.  And from there, the user has a link to Launchpad.  At the moment, I can think of maybe putting bullet points at the top of that page, including the main things which are needed in a bug report....and then below the bullet points, the link to LP, and below that put everything else.  

That might make it more of a streamlined process, for people who take that route to reporting.  Because I suspect users are taking the link in the first sentence to LP, and not reading the page.  (I could write up a proposed edit for that page, if you think it would help.  I would make the bullet list at the top, and only put the link below it.  And then flesh out a bit more below that.)

When people first post in a forum about a possible bug, we always, without fail, instruct them what needs to be included in the bug report.  I sometimes link to that page, but usually I just type the instructions in the forum message.  I can't speak for everyone, but personally, if I've urged someone to report a bug, and they do, I double-check to make sure they included everything.

When people first post in social media....well, that's where the request came from, for a flowchart type of document (I'm assuming it would be something like a flowchart, or numbered steps, or something very structured), which would allow newbies to figure out whether what they have found is a bug or not, and how to report it.  Otherwise, I'm not sure if there is any good route for social media users to get to, or find instructions about, reporting a bug.

Although that request was brought to the first meeting of the Vectors team, it doesn't look like it was ever documented in an Issue, in the Vectors team gitlab account.  Personally, I'm not sure if that would be the best solution.  But on the other hand, creating the Issue would make a place for it to be discussed further.

What would you think about something like that?

So let's see, we have a route for reporting a bug directly from inside Inkscape (Help menu), and we have a route from forums.  We don't really have a route (that I know of) for social media users to learn how and to write bug reports.  But we have a proposal for the flowchart type of webpage, which potentially could serve everyone.

And the other route which is not covered is someone who does not see the Help menu item, who already knows about the LP bug tracker, and just browses here independantly (not via link).  If we could put a link on the new bug report form to the website page, that would cover this route to reporting a bug, as well as if someone is coming from social media.

Would that work?

I can't say anything new or different about the 15 lines worth of warning symbols and explanation points, than I said before.  I just think there must be a more friendly and inviting way to get users involved in reporting bugs correctly.