[Bug 24071] New: Ask for complete information when opening a bug report
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24071 Bug ID: 24071 Summary: Ask for complete information when opening a bug report Change sponsored?: --- Product: Project Infrastructure Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Bugzilla Assignee: jonathan.druart@bugs.koha-community.org Reporter: jonathan.druart@bugs.koha-community.org I would like to patch our bug tracker to display a message about which information they need to provide in the description of the bug. * They should give the FULL version number, most of the time they only provide the major version, we will need to point to a link explaining how to get the exact version ("See the about page" I guess) * Check the log on the server (with the full error) * The JS console (if it's a UI issue) * Version of the OS * Version of DBMS (if related) What more? How could it be done to make them retrieve the info easily? Going further, what about a new area in Koha to post an issue, we could retrieve the correct info we need and open a new bug report for them? (but... spam, support companies, too easy and so will skip ML, etc.) -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24071 Jonathan Druart <jonathan.druart@bugs.koha-community.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |In Discussion CC| |katrin.fischer@bsz-bw.de, | |martin.renvoize@ptfs-europe | |.com, | |nick@bywatersolutions.com, | |tomascohen@gmail.com -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24071 Lisette Scheer <lisetteslatah@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |lisetteslatah@gmail.com -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24071 --- Comment #1 from Katrin Fischer <katrin.fischer@bsz-bw.de> --- I think we should not overcomplicate filing a bug report as it's already proven to be a hurdle to a lot of people I talked to. I didn't think it was, so was really surprised at first, but people are a bit 'scared' of bugzilla at the moment. I think if we add more technical requirements, it will just make it even worse. What we could do: Add information pages on how to retrieve the information you mentioned to the wiki or the manual and point to them whenever we need them. So let's say someone filed a bug, that is not clear in itself, we can have the bug wranglers ask for the information and use the links with detailed explanations on how to do it. -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24071 --- Comment #2 from Jonathan Druart <jonathan.druart@bugs.koha-community.org> --- What I was suggesting is to ask them to copy/paste a given block of info from about.pl for instance, that would not require any technical skills or extra complications. -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24071 --- Comment #3 from Martin Renvoize <martin.renvoize@ptfs-europe.com> --- I like the templates you can use in github issues.. shame bugzilla doesn't support similar. -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24071 --- Comment #4 from Katrin Fischer <katrin.fischer@bsz-bw.de> --- I think we are not far apart - I just don't want to up the requirements. It should still be possible to file a simple bug, growing into the process. We can still ask for more and help people to retrieve this information. - version (easy, about page) - logs (hard, especially since some can't access their servers on this level) - Js console (middle) - OS version (easy, about page) - DBMS (easy, about page) Should we add a copy button to the about page that makes it really easy to get a nicely formatted summary? -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24071 --- Comment #5 from Jonathan Druart <jonathan.druart@bugs.koha-community.org> --- Created attachment 99180 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=99180&action=edit Bug 24071: Add a way to export debug info Actually this patch does much more, but still not enough. There are 2 goals that I would like to achieve with this patch: * Add an entry point to the Koha wiki from Koha * Explain a bit how to report a from within Koha, and export useful data TODO: * Stylish * Fix wording * Improve exported file (must be either a .txt or .zip with other text files, not a .pdf) * Display other log files, not only plack-error.log * Display the bottom of the log file, not the beginning * Only display the last X lines of the logs (500?) * Is there a way to retrieve the content of the JS console (sounds impossible to get it from other tabs anyway, unless we copy it in the local storage, which seems wrong). * Main question: how critical it is to display the log file? Is that ok to display it for superlibrarian only? They will need to be warned that the file could contain potential data they do not want to share publicly (IP, DB name, etc.). -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24071 --- Comment #6 from Jonathan Druart <jonathan.druart@bugs.koha-community.org> --- (In reply to Jonathan Druart from comment #0)
Going further, what about a new area in Koha to post an issue, we could retrieve the correct info we need and open a new bug report for them? (but... spam, support companies, too easy and so will skip ML, etc.)
This last patch is more or less what I had in mind. Submitted to open/continue the discussion. What it looks like (quite ugly, needs to be styled): https://snipboard.io/OdjLr5.jpg -- You are receiving this mail because: You are watching all bug changes.
participants (1)
-
bugzilla-daemon＠bugs.koha-community.org