Kunda1 wrote:I started a rudimentary flow chart that I'm hoping may help improve the quality of bug reporting (especially for bug triagers).
It's a google drawing. I don't know any flow chart etiquette or techniques so I was hoping that with some help we could spruce this up and then post it somewhere prominent that people can quickly reference.
I think this is where the process breaks down. An average user, let alone a new user doesn't have the knowledge to answer this question. Of course it's a bug, the program doesn't work as I expect, and it's of the highest priority because it's blocking my work. I think the user should post on the forum (new topic or responding to an existing topic) early in the process, prior to creating a ticket on the tracker. As an example I would use DeepSOIC and NormandC as examples. Two people that are most qualified to answer the question "Are you sure it's a bug?" and most likely to triage in the forum before creating a ticket.Kunda1 wrote:Are you sure it's a bug?
Include everything listed at freecadweb.org/wiki/bug_reporting#requirements because we'll ask for it anyway
triplus wrote:I like the idea of having such chart. But i do feel your proposal @Kunda1 lacks a few days of work. I understand you are after more collaboration. But this feels like a project you can do yourself if you put some muscle into it. As for suggestions simplify it and style it a bit better.
triplus wrote:a few days of work
Kunda1 wrote:Integrating @ sgrogan's advice
sgrogan wrote:Kunda1 wrote:Integrating @ sgrogan's advice
Thanks for reading and understanding my post. Trade "lazy" for "can't find it"?