LibreOffice 3.3.0 - OOO330m19 (Build:6) - tag libreoffice-3.3.0.4 [Debian Lenny] hi there, I am a long-term Linux enthusiast, and over all overwhelmed by the new features that LibreOffice sports over Openoffice. But, then, I found it quite complicated to get here. I suggest adding a menu entry to send people directly to this BTS. And directly should mean, not having to spot the string "LibreOffice" among hundred of other product names (like xprint), if possible. Furthermore, I start wondering if to report bugs towards LO or rather against OOo while the major amount of code is still from there...? Cheers and good luck! Ralf.
*** Bug 35898 has been marked as a duplicate of this bug. ***
Is there any proven experience from another software that such a link will improve bug fixing process? I am concerned that this only will raise a flood of non-bugs and duplicates. Currently I do not see a problem with too many unreported bugs, but, of course, evaluation is difficult. A link to a page like <http://filezilla-project.org/support.php?type=client&mode=bugreport&version=3.4.0> might be acceptable. Corresponding OOo issue: "Add 'report a bug' in help menu" <http://openoffice.org/bugzilla/show_bug.cgi?id=53861>
Confirmed by lots of complaints. For a long time I thought that users should be able to find our Bugzilla without problems, but in between I doubt. Today I got a mail from a user who was able to repair "mailmerge.py" for his needs, but was neaby unable to find our bug tracking system. I believe a direct link to manual page <http://wiki.documentfoundation.org/BugReport> (please see attached mockup) can not damage and might help. @libreoffice-ux-advise@lists.freedesktop.org What do you think?
Created attachment 48633 [details] Mockup, see Comment 3
Created attachment 48639 [details] Mockup, see Comment 3 Old mockup with wrong link
I think it may be part of a solution - due to the discussions on several lists (in the last months), I think we have to consider some more people with different background (let's say "people with less experience"). Personally, I'd like to get their feedback as well. Proposal: * Links ("Send Feedback ...") in the help menu and the StartCenter get added which refer to a new website. * The website allows some tweaking even after the release of the user's LibO version. * This website may contain varying items based on what is interesting to the project: * Link to the Bugtracker --> either the plain tracker or the Simple Bug Form some guy was working on on the libo-dev list (although I tried to help, I'm not sure what the current status is) * Link to recent user surveys --> Björn B. is currently working on user surveys within the Design Team * Link to the mailing lists or forums --> to attract people to join the community * ... Is this something that sounds reasonable? If yes, then I can start some documentation on that. Just ping me ...
(In reply to comment #6) > Is this something that sounds reasonable? If yes, then I can start some > documentation on that. Just ping me ... Yes, great. I discovered some new possibilities: On the Bug Report Manual Wiki page <http://wiki.documentfoundation.org/BugReport_Details#Extensions> I created an experimental link to the Bugzilla "Report a new Bug" page what will additionally transfer some settings to Bugzilla. For example + the Initial Bug Status will be UNCONFIRMED instead of NEW + no Version will be selected, so Bugzilla will reject the report if the reporter did not select a version wittingly. May be other settings also should be transferred, and experience from that links can be used for a LibO Bug report Wizard
@Christoph: We have a new situation with an upcoming project "Bug Report Assistant". for Details please see a.m. link!
https://bugassistant.libreoffice.org/libreoffice/bug/bug.html will be made available under an iframe at https://www.libreoffice.org/get-help/bug/ (can be viewed already at https://www.libreoffice.org/get-help/bug/?stage=Stage after login in silverstripe ) before september 26, 2011. It should be tested as much as possible in the meantime. It matches the second milestone set at http://wiki.documentfoundation.org/Bug_Submission_Assistant#Milestone_0.2
https://www.libreoffice.org/get-help/bug/ is live
@Loic: I believe there is some misunderstanding, or will I really see a menu item similar to my attached mockup in the next master build?
Sorry about that. I thought it was about the web site, not the software. Thanks for correcting me.
Created attachment 53104 [details] mockup2.pdf New, enhanced mockup showing modified Menu item and Feedback draft page
Created attachment 53124 [details] Bug Submission Assistant Workflow incl. Help Menu Item Rainer, I noticed your mockups about the menu / website integration. I already spend some time on such a proposal during the work on the Bug Submission Assistant. It includes: * "Provide Feedback..." menu command * Revised help menu (makes sense to clean up this as well) * Structure of the landing page incl. support / survey stuff incl. close-to-final help texts The original mockup is located here: http://wiki.documentfoundation.org/Bug_Submission_Assistant_-_ToDo#Web_design Please also note that the link should not lead to a fixed URL, but should be routed via the "website stable link forwarding", see the thread on the website mailing list: http://www.mail-archive.com/website@global.libreoffice.org/msg06232.html Some comments on your proposal "53104: mockup2.pdf" from an UX point-of-view: * The hierarchy of "Get Help - Feedback - Bug Report" doesn't seem to fit here, although we add "Provide Feedback..." to the LibO help menu (because there is no alternative) -> it should rather be feedback.libreoffice.org or www.libreoffice.org/feedback Proposal: Should the details be worked out a Design whiteboard page (maybe easier than a discussion in this bug)?
@Christoph: all your comments and proposals meet exactly with my intentions. My mockup only should show shat kind of contents I'm thinking about, because it seems that there still might be some misunderstanding; I had asked on website mailing list for a stable URL (website stable link forwarding) , my latest posting here: <http://www.mail-archive.com/website@global.libreoffice.org/msg06282.html>. I would be glad if you could handle that due to your proposal.
Since all new unconfirmed bugs start in state UNCONFIRMED now and old unconfirmed bugs were moved to NEEDINFO with a explanatory comment, all bugs promoted above those bug states to NEW and later are automatically confirmed making the CONFIRMED whiteboard status redundant. Thus it will be removed.
2012-01-15 we have a working forward to the assistant so that the Menu item can be created. The further steps due to workflow sheet can be integrated one by one later. @Christoph: Thank you for detailed workflow suggestions @Ivan: Can you please create the Help menu item with a link to <http://hub.libreoffice.org/file-a-bug/>? Please mention that it's planned to forward additional information with that link in future, like UI language, OS or similar. Please feel free to reassign (or reset Assignee to default) if it’s not your area or if provided information is not sufficient. Please set Status to ASSIGNED if you accept this Bug.
(In reply to comment #17) > @Ivan: > Can you please create the Help menu item with a link to > <http://hub.libreoffice.org/file-a-bug/>? A task for 3.6, right? UI freeze date for 3.5 was Jan 9 IIRC.
> A task for 3.6, right? UI freeze date for 3.5 was Jan 9 IIRC. We will see, more 3.5.1, or even 3.5.0. Currently I would be happy to have it in Master.
Well, if some evil will not befall, I'll have done this task towards the end of the week... Rainer, should I follow the [awesome!] mockup from Christoph, i.e. use the "Provide Feedback..." name for the new item and move/rename other items?
(In reply to comment #17) > @Christoph: > Thank you for detailed workflow suggestions > > @Ivan: > Can you please create the Help menu item with a link to > <http://hub.libreoffice.org/file-a-bug/>? Please mention that it's planned to > forward additional information with that link in future, like UI language, OS > or similar. I just noticed that the scary whiteboard page containing the proposed behavior for the "complete functionality" hasn't been added yet. By the way, this stuff has already been discussed with Christian and Florian. So, finally: http://wiki.documentfoundation.org/Design/Whiteboard/LibreOffice_Send_Feedback @ Rainer: Should this be added as the URL of the bug instead of QA incubator? @ Ivan: Thanks for your help!!! :-)
@Ivan: I'm an awful style scout, keep close to Christophs mockups, but mention that already withthe second picture "Provide Feedback" we are on the Website (Bug 44795), starting with "screenshot"- picture "Rpeort a problem - preparation" the Assistant would be affected; I believe those are suggestions for further Assistant design and function improvement.
Please remove my e-mail-address from your list. bugzilla-daemon@freedesktop.org schrieb: > https://bugs.freedesktop.org/show_bug.cgi?id=35855 > > --- Comment #22 from Rainer Bielefeld <LibreOffice@bielefeldundbuss.de> 2012-01-16 10:46:41 PST --- > @Ivan: > I'm an awful style scout, keep close to Christophs mockups, but mention that > already withthe second picture "Provide Feedback" we are on the Website (Bug > 44795), starting with "screenshot"- picture "Rpeort a problem - preparation" > the Assistant would be affected; I believe those are suggestions for further > Assistant design and function improvement. >
Bitte entfernen Sie meine E-Mail aus Ihrem Newsletterversand. bugzilla-daemon@freedesktop.org schrieb: > https://bugs.freedesktop.org/show_bug.cgi?id=35855 > > --- Comment #19 from Rainer Bielefeld <LibreOffice@bielefeldundbuss.de> 2012-01-15 09:01:15 PST --- >> A task for 3.6, right? UI freeze date for 3.5 was Jan 9 IIRC. > We will see, more 3.5.1, or even 3.5.0. Currently I would be happy to have it > in Master. >
I'll tell Lars by mail how to do that.
Some initial work in the master branch: http://cgit.freedesktop.org/libreoffice/core/commit/?id=924d0bdd47ed895592332714be8ee32afe1acebb
Removing Lars from CC since he's still in there...
This feature has been added already a while ago.