[Libreoffice-bugs] [Bug 142831] New: 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

            Bug ID: 142831
           Summary: Develop a new bug-reporting functionality and a new
                    top-level "Bugs" menu item in the menu bar
           Product: LibreOffice
           Version: 7.1.3.2 release
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: medium
         Component: LibreOffice
          Assignee: libreoffice-bugs at lists.freedesktop.org
          Reporter: mleonov at protonmail.ch

Description:
UX Rationale: Currently there is Help > Send Feedback > Create a bug report
- this is too many layers of hiding bug reporting. Moreover, a vast majority of
LibreOffice users have never heard the words "bug report", so this will not
generate the desired bug-reporting behavior on LibreOffice's intended user
base. If users are important to LibreOffice, so are the bugs they report!
TASKS:
1. Add a top-level "Bugs" menu entry to the right of "Help" as a continuation
of the top-level menu of LibreOffice.
2. Move the following submenu item here: "Help" > "Send Feedback" so that it
serves as a placeholder while the following new features are being worked on -
"Catch a Bug" and "View My Bugs" (when these are released, deprecate "Send
Feedback").
3. Add two sub-entries to the new "Bugs" menu:
3.a > "Catch a Bug"
3.b > "View My Bugs"
4. At the left end of the upper row of buttons, add a by-default-visible button
with a Ladybug icon and tooltip text "Catch a Bug" (same action as "Catch a
Bug" in the top "Bugs" menu - to provide one more UI entry point).
5. For "Catch a Bug", keep the bug report creation inside the LibreOffice UI,
for example a separate window, without redirecting to any website.
6. Consider using an API to get the report created on
https://bugs.documentfoundation.org/.
7. When the user submits a "Catch a Bug" report through the LibreOffice UI
window, the unique numeric ID of the bug is generated as usual and the
full-path link to the new bug report is added to the "View My Bugs" menu.
8. In the bug-submitting UI of "Catch a Bug", notify the user in UI text that
the data the user is submitting is anonymous - no personal data is needed from
the user, the unique and automatically generated bug id will be most important
to all.
9. Make all the information from the "About LibreOffice" window used, displayed
(for transparency toward the user), and submitted as automatically added,
non-removable, uneditable metadata for the bug report.
10. Make the LibreOffice application type (Writer), in other words which
application from the LibreOffice suite, get automatically added to the body of
the report.
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. 
13. Make all bug reports submitted from this installed LibreOffice instance
appear as a list of links in "View My Bugs" by clicking which the user can
revisit the unique bug report page on https://bugs.documentfoundation.org/
whenever wishing to check for progress or outcome or respond by providing more
details in the bug page.
14. Reuse the "Recent Documents" UI elements from the "File" menu (where each
recent document's file name is displayed) in "View My Bugs" as links to the
user-opened bugs.
15. Make each bug report's "Summary" line text appear as the menu label over
each bug link in "View My Bugs". This is the bug report "Summary" line text
that the user fills when creating the bug report within the LibreOffice UI and
that will appear as the "Summary" line on the unique bug page on
https://bugs.documentfoundation.org/.
16. In "View My Bugs", add a way for the user to easily remove any of the bug
entries (links) any time (the respective bug report pages on
https://bugs.documentfoundation.org/ will continue to exist independently).
Initially, copy the "Clear list" functionality from "Recent Documents"; plan to
add functionality to remove specific items (as opposed to all in "Clear list").
17. In "View My Bugs", add a functionality placeholder for an API to check for
updates on the bug page on https://bugs.documentfoundation.org/ for each bug
link in the "View My Bugs" menu every time this LibreOffice application is
started. Whenever there is an update on the bug page, a UI marker appears for
each bug (this can be accomplished by a symbol prepended to the bug label in
the menu or a change to the color of the bug label text in the menu. This
functionality will enable https://bugs.documentfoundation.org/ to keep in touch
(if needed) with this particular user of LibreOffice as well as to inform the
user of any progress on any bug that this user reported.

Steps to Reproduce:
...

Actual Results:
...

Expected Results:
...


Reproducible: Always


User Profile Reset: No



Additional Info:
...

-- 
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/20210612/e1048c8a/attachment-0001.htm>