Apache OpenOffice (AOO) Bugzilla – Full Text Issue Listing
|Summary:||Add "Feedback" link as Help item|
|Product:||General||Reporter:||Brennan Novak <hi>|
|Component:||ui||Assignee:||AOO issues mailing list <issues>|
|Status:||CONFIRMED ---||QA Contact:|
|Priority:||P3||CC:||ingenstans, oooforum, pescetti, rainerbielefeld_ooo_qa, uwefis|
|Version:||3.3.0 or older (OOo)|
|Issue Type:||FEATURE||Latest Confirmation in:||---|
Description Brennan Novak 2014-05-08 12:54:40 UTC
Created attachment 83358 [details] Screenshot of file bug report suggestion Hello. I've been using OO on my Mac but I find it to be very buggy. But being a good steward / FOSS developer / UX designer I want to participate and I want to help improve things. However, it took me 25 minutes of my time figuring out just "how" to file a bug report this morning. Creating the actual bug report was only 5 mins with my normal UX flow with other FOSS projects on Github. Attached below is an image of what I feel would greatly improve the ability for caring & intelligent users to help improve OO. I also discovered this similar issue #89317 where it seems a similar idea was brought up... I agree, a button cluttering up the actual UI would be a bad idea, but tucking a link to the Bugzilla would be significantly better than the 10+ steps it currently takes to learn how to file a bug. Hopefully you will reconsider this improvement!
Comment 1 Rainer Bielefeld 2014-05-08 13:26:01 UTC
I have some ideas with a template collecting some minimum information from AOO installation and helping user to submit AOO bugs instead of bugs with users, but it will still take some weeks until I will be able to present a draft for further discussion and improvement. Some minimum guide will be required, otherwise too many help requests will be submitted as issue report.
Comment 2 Brennan Novak 2014-05-08 13:39:29 UTC
I don't really understand what you mean by "submit AOO bugs instead of bugs with users" or how that hooks into the user experience of OO and trying to submit valid feedback. Your approach sounds like a lot more work than mine. All I am asking for is something relatively simple that seems like it would help the process of giving valid feedback!
Comment 3 Rainer Bielefeld 2014-05-16 04:39:18 UTC
*** Issue 124912 has been marked as a duplicate of this issue. ***
Comment 4 Rainer Bielefeld 2014-05-16 05:15:13 UTC
There can't be any doubt that we urgently need improvement for feedback directly from AOO, Andrea Pescetti tells about the currently very uninviting way in Issue 124912. But that can't be done with a simple link to Bugzilla as a Help menu item: (a) for very many users BZ is MUCH too mysterious, they might not want to create a Bugzilla account and so on (b) Most users simply without some training or at least having read a short manual will not be able to do a useful bug report. We would get 5% more bug useful reports and 5 times as many completely useless reports, whining, help requests of users what are even unable to ask Google (see DUPs of Issue 119006!). So I recommend not to be too inviting for bug reports directly in BZ What we need is a Feedback Page similar too <http://www.libreoffice.org/get-help/feedback/> What leads users with short and pregnant hints to the feedback he wants to do: * Get Help * share a Like on Facebook * Follow AOO on Twitter * Report a bug * Join a mailing List in his language * Whatever else We should start a draft in Wiki or cwiki, we need the page before we add the Help Item. The "Report a Bug" invitation should have 4 text lines or so like "AOO has a public Bug tracking service ... every interested user ... great possibility to improve the software you use ..." and 3 Links: - I already have experience with bug tracking in Bugzilla directly to issues.apache.org/ - I am new here: Link to something similar to <https://wiki.openoffice.org/wiki/QA/HowToFileIssue#Principles> ... Preliminaries ... Reporting a New Bug - That's all to sophisticated for me, I want to tell my observations by email so that an expert can have a look -- Link To Bugzilla -- Link to "I want to learn more" Before we start to invite unexperienced users to report bugs we urgently need to improve our manuals. Currently we have information scattered on <http://qa.openoffice.org/issue_handling/pre_submission.html>, <http://www.openoffice.org/bugs/bug_writing_guidelines.html>, <http://wiki.openoffice.org/wiki/QA/HowToFileIssue> and may be somewhere else. If the infrastructure requirements are done the creation of the Help item will be simple. And in this contents please see my Comment 1 what would be an AOO built in alternative approach to the LibreOffice Bug report assistant.
Comment 5 Andrea Pescetti 2014-05-16 09:31:57 UTC
Sorry for the duplication of information, the persisting e-mail delays are not helping the conversation. I confirm that indeed my issue is exactly the same as Brennan's and originated from his message. Note that there is work to do on several different scenarios: 1) Going from the application to a section of the website related to Feedback. This is what the current issue is about. Our best landing page at the moment is http://www.openoffice.org/contact_us.html and already has the right structure, so this seems something we can do without thinking too much about it. Note: most of the people who will use this feature will stop before hitting Bugzilla, since they will find an answer in the Forum. 2) Consolidating our web pages about bug reporting. This needs to be done and Brennan's odyssey through all the OpenOffice sites is a good example. But this is a separate issue. 3) Making Bugzilla easier to use with better (or more visible) reporting guidelines, less cluttered report screens, even in-app tools. Again, this is a separate issue. I also prefer "Feedback" to "Report a bug" since it is more generic but equally understandable. But I'd like to hear from Brennan on this.
Comment 6 Rainer Bielefeld 2014-05-16 10:58:33 UTC
1): Yes, that is a base we can use. Looks a little "uncool", and contains some but all we need is in it. Contents has some mistakes and some unreasonable hurdles for normal users, but that can be fixed easily. I will create some suggestions during Weekend 2): That really is a a serious problem, we simply have much too few manpower for that task. I hope that with more feedback via that link some more volunteers will come to AOO for all those tasks So we only need to define to where the Link in Help menu should lead. I prefer something virtual what normally forwards to the feedback page and sometimes (new release, other events, infrastructure problems to somewhere else.
Comment 7 Ariel Constenla-Haile 2014-05-17 08:25:37 UTC
Firefox has a "Submit Feedback..." menu item, that leads to https://input.mozilla.org/en-US/feedback with a very simple UI
Comment 8 Rainer Bielefeld 2014-05-17 08:55:08 UTC
(In reply to Ariel Constenla-Haile from comment #7) Yes, that's the direction we should go. I would prefer a little more contents, but we should not overwhelm users immediately at the entrance door with such "subscribe dev-list" and similar. But my opinion is that the CSS problems ("Issue 124400 - Website: styles.css related headings do not look like headings" and others) of AOO website should be fixed before we create new pages.
Comment 9 oooforum (fr) 2019-10-13 10:14:47 UTC
*** Issue 64212 has been marked as a duplicate of this issue. ***
Comment 10 oooforum (fr) 2019-10-13 10:19:39 UTC
Feedback from end-users is not just a feature. Where these reports goes and who replies to them?