https://bugs.documentfoundation.org/show_bug.cgi?id=143700
Stéphane Guillou (stragu) <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |stephane.guillou@libreoffic | |e.org --- Comment #5 from Stéphane Guillou (stragu) <[email protected]> --- Also note that for crashing issues, crash reports already include a signature that makes it easier to link reports to each other, and metadata that contains the last 4 UNO commands used. See for example the Metadata tab in https://crashreport.libreoffice.org/stats/crash_details/e0ef61ce-4916-41f9-9d30-1f57c5cb1579 I understand that a precise ID would help the search queries, and that UI strings do evolve over the years, but I agree with Buovjaga here that the effort to get a "normal" user to provide such information would be as much (if not more) effort as the QA contributor doing it themself. We can't include these command IDs by default in the UI for obvious reasons, so the most efficient workflow would be to tell the bug reporter to "please include the ID by turning on an expert configuration option in the settings, restarting LO and repeating the steps". It might even scare off some reporters who already find Bugzilla daunting... Because the reporting of bugs is to be done in English, the command is usually easily identifiable. And if it isn't, QA contributors will add the name in English in the comments or summary – sometimes even with the corresponding UNO command. (In reply to Colin from comment #2) > Perhaps a permanent log file to identify any changes as they are made to the > underlying options could help in both the identification and recovery from > profile corruption. I'd recommend reporting this idea separately. -- You are receiving this mail because: You are the assignee for the bug.
