[Libreoffice-bugs] [Bug 142831] Develop a new bug-reporting functionality and a new top-level "Bugs" menu item in the menu bar

[bugzilla-daemon at bugs.documentfoundation.org]

https://bugs.documentfoundation.org/show_bug.cgi?id=142831

--- Comment #11 from Max L. <mleonov at protonmail.ch> ---
(In reply to Max L. from comment #10)
> (In reply to Heiko Tietze from comment #7)
> > (In reply to Max L. from comment #0)
> > To see your bugs you need to know the account. Sounds like a
> > security/privacy topic if added to the application.
> I am well aware of that, but it is my belief that LibreOffice has to
> reinvent how it collects bug data, because the Document Foundation can
> neither afford a qualified QE workforce nor scale down the total number of
> application features that in combination produce bugs.
> 
> Such features as these (copied from the description) can be steps in that
> direction - if you start receiving bug reports with patterns of same
> features malfunctioning, you have much more data at your disposal while
> still missing the QE workforce. It's not automation, it's not machine
> learning, it's about finding a clever way of getting the needed data when
> bugs start to appear:
> 
> 11. Make the LibreOffice application copy the history into this report of a
> (configurable for the future) recent number of operations that appear in the
> Undo menu. Remove (to anonymize) all text that appears as part of any recent
> operation that involves text manipulation (example: "Undo: Typing
> "abcdefgh""). This history (along with the LibreOffice version details in
> the previous point here) must be visible (as has been copied) to the user in
> the bug report filling window of LibreOffice when the user is checking the
> contents of the bug report before clicking Send.
> 12. Reuse the code from LibreOffice's feature "Help" > "What's This?" as
> part of LibreOffice's internal workflow to enable the user to point and
> click and thus have the relevant feature(s) entered into the bug report
> without the user having to name these features.

When you have the data, you can filter it and recognize the patterns - like
what is currently done with reported crashes of LibreOffice.

BTW, the above was in response to:
(In reply to Heiko Tietze from comment #7)
"Bug reporting is an art beyond point and click. It's hard to summarize the use
case so everyone understands the intention, to describe in a concise but
complete way, and eventually to transparently track the patch, to organize the
work, to prioritize by requests etc."

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/libreoffice-bugs/attachments/20210614/b1163751/attachment.htm>