<html> <head> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> </head> <body> <div class="moz-cite-prefix">On 9/11/22 10:35, Stéphane Guillou wrote: </div> <blockquote type="cite" cite="mid:455298cf-82fe-c823-8583-1ee41a4f49a1@libreoffice.org"> <meta http-equiv="content-type" content="text/html; charset=UTF-8"> Hi all About reporting bugs for LO: we currently have two forms (that I know of) that people might land on. 1. Directly from Bugzilla: <a class="moz-txt-link-freetext" href="https://bugs.documentfoundation.org/enter_bug.cgi?product=LibreOffice&format=guided" moz-do-not-send="true">https://bugs.documentfoundation.org/enter_bug.cgi?product=LibreOffice&format=guided</a> 2. Linked from the Wiki: <a class="moz-txt-link-freetext" href="https://bugs.documentfoundation.org/enter_bug.cgi?product=LibreOffice;bug_status=UNCONFIRMED;version=" moz-do-not-send="true">https://bugs.documentfoundation.org/enter_bug.cgi?product=LibreOffice;bug_status=UNCONFIRMED;version=</a>? The first one is the "guided" format, which is great for providing the important bits like steps, results, version info, etc. with extra explanatory text. But it doesn't allow directly adding extra fields and attachments. The second one doesn't have the broken down description that will be helpful to provide essential info, but it does allow directly adding an attachment and extra fields like keywords, URL, Blocks, See also... To me, the second one is only really good for more advanced users, and to reduce noise of successive edits. Newcomers should use the first one because it is clearer, it has plain text explanations that guide them, and it makes it less likely that they will use fields in the wrong way (and that they will find it too advanced for them). However, I believe the most important piece it is missing is the attachment field. I'm sure there's quite a few things we could do to improve the situation, but could we start with adding the Attachment field to the guided format so bug reporters are incentivised to provide testing files and avoid some back-and-forth? The form currently has the following text: <blockquote> IMPORTANT: In case you need to attach to the bug, Please use the "Add an Attachment" link once the bug is filled. </blockquote> Is that because there was a limitation to add the attachment field? Cheers! </blockquote> Oh, and I forgot to mention another extremely important feature of the more detailed form: the Possible duplicates that appear below! That would save us a lot of time categorising duplicates. Would it also possible to add that to the new guided form? Cheers <pre class="moz-signature" cols="72">-- Stéphane Guillou Quality Assurance Analyst | The Document Foundation Email: <a class="moz-txt-link-abbreviated" href="mailto:stephane.guillou@libreoffice.org">stephane.guillou@libreoffice.org</a> Mobile (France): +33 7 79 67 18 72 Matrix: @stragu:matrix.org Fediverse: @stragu@mastodon.indie.host Web: <a class="moz-txt-link-freetext" href="https://stragu.gitlab.io/">https://stragu.gitlab.io/</a></pre> </body> </html>