Welcome to the club.Kunda1 wrote:honestly, charts are not my strong suite
Something like that would do it for me. After i guess somebody would put a few days of work in it to figure out all the remaining details.
Welcome to the club.Kunda1 wrote:honestly, charts are not my strong suite
Good cut and paste though. Good point on your markup, if you know it's been reported you got the info from somewhere.triplus wrote:Welcome to the club.
You are right, It can't be switched off and I didn't bother to take my gimp out. I will edit the post above.triplus wrote:The Style has improved but i don't like the fact we need to have watermark of some software at the bottom? Not a big problem but i do see room for improvement here.
All these charts are very space consuming which is another good reason to not making them too complex.As for the flow. You included 2 new categories in the chart. And once done the chart will likely become too complex to be useful to an average issue reporter. As this is what we are after? Horizontal approach could end up being useful if used as a header image on bug tracker at some point in the future.
Would you mind if I put it in the list of what to attach to the bug report? (I'm still trying to not have it centered).As for having special simplify entry mentioned in the flow. To signal this is more important step compared to some other ones. I don't feel that is needed and we shouldn't bother the reporter with endless demands. Like some rocket science stuff is involved in the process.
Now that I think about it that is a very difficult one. We can have at this exit (at least):bejant wrote:"Error" and "no error" might be ambiguous as it doesn't describe where the error occurs.
An similar example but not 100% related to this topic, see how the OCC tracker displays their bug cycle workflow: Maybe we can make a header that is collapsible in the tracker that would display whatever chart we decide 'makes the cut' ?triplus wrote: Who knows maybe it could be used as a banner on issue tracker in the future.
I agree with triplus. I think we are trying to do two things at once.triplus wrote:Yes something like that. But note that is a different effort and it is not directly related to the one in this thread. We are still after the final result in this thread.
Result we could consider to be a stylish and simple to understand flow chart giving basic information on how an average user should/could attempt to report a bug. That goal wasn't achieved yet.