Page 3 of 5

Re: Request for collaboration: Creating a visual flow chart for reporting bugs

Posted: Sun Feb 26, 2017 3:34 pm
by triplus
Now when we known what needs to be done somebody will need to take the lead and dictate the changes through. Preferably one of the potential new contributors that haven't done something like that in the past yet.

Re: Request for collaboration: Creating a visual flow chart for reporting bugs

Posted: Tue Feb 28, 2017 11:08 pm
by Kunda1
I'm thinking that having the
simple flow chart for a new/average user to deal with a bug/potential bug
to be visible on the tracker would be ideal. So I'm thinking of how to design it to fit our current tracker...again not my strength but I'm inspired by all the feedback in this thread so far.

Re: Request for collaboration: Creating a visual flow chart for reporting bugs

Posted: Wed Mar 01, 2017 12:13 am
by triplus
Kunda1 wrote:again not my strength
Or you could look at it like this. Five years back i asked a question:

https://forum.freecadweb.org/viewtopic.php?t=2203

And i still haven't figure it out:

https://forum.freecadweb.org/viewtopic.php?f=22&t=16954

P.S. Start up Inkscape and try to create something horizontal and compact (based on the feedback gathered). You can rest assured that after few days of working on it (and after you decide to share the result) it will be properly evaluated.

Re: Request for collaboration: Creating a visual flow chart for reporting bugs

Posted: Wed Mar 22, 2017 9:57 pm
by chrisb
Here is a proposal with a pure horizontal layout to keep the height small.
I used different colors for users and developers, so the user can see, that it is only the developers responsibility to close the ticket, the user is not asked for confirmation.
The second step could be extended and both paths could be flowing together to have a common task with the forum discussion, but I hope this simple diagram can transport the message better.

Re: Request for collaboration: Creating a visual flow chart for reporting bugs

Posted: Thu Mar 23, 2017 11:26 am
by Kunda1
chrisb wrote:Here is a proposal with a pure horizontal layout to keep the height small.
I used different colors for users and developers, so the user can see, that it is only the developers responsibility to close the ticket, the user is not asked for confirmation.
The second step could be extended and both paths could be flowing together to have a common task with the forum discussion, but I hope this simple diagram can transport the message better.
+1

Re: Request for collaboration: Creating a visual flow chart for reporting bugs

Posted: Fri Mar 24, 2017 12:11 am
by triplus
chrisb wrote:Here is a proposal with a pure horizontal layout to keep the height small.
Amazing.

Re: Request for collaboration: Creating a visual flow chart for reporting bugs

Posted: Fri Mar 24, 2017 1:00 am
by kkremitzki
chrisb wrote:Here is a proposal with a pure horizontal layout to keep the height small.
I used different colors for users and developers, so the user can see, that it is only the developers responsibility to close the ticket, the user is not asked for confirmation.
The second step could be extended and both paths could be flowing together to have a common task with the forum discussion, but I hope this simple diagram can transport the message better.
This looks very good, I would just suggest "if already reported" rather than "if reported before" and "issue to be reported" over "error to be reported"

Re: Request for collaboration: Creating a visual flow chart for reporting bugs

Posted: Fri Mar 24, 2017 1:14 am
by chrisb
kkremitzki wrote: This looks very good, I would just suggest "if already reported" rather than "if reported before" and "issue to be reported" over "error to be reported"

Re: Request for collaboration: Creating a visual flow chart for reporting bugs

Posted: Thu Apr 13, 2017 7:20 pm
by chrisb
Is it possible to make a forum discussion mandatory before creating a ticket? I have seen here lately several posts which have been created afterwards. If possible the link to an existing discussion could be a mandatory field, although I am afraid there is no way out of these "I have been told to create this forum post or else I couldn't create a ticket"-posts.

Re: Request for collaboration: Creating a visual flow chart for reporting bugs

Posted: Thu Apr 13, 2017 10:48 pm
by triplus
If forum thread is created i don't see real issue here. As if it turns out it was false alarm the issue simply gets closed and that is that.

P.S. Where (and how) to put visual flow chart created in this thread to better facilitate reporting bugs. That likely is a more interesting question.