Summary: | BUGZILLAASSISTANT: forward libreoffice.org/bugzilla to bugs.freedesktop.org so there's not two separate entry points for users | ||
---|---|---|---|
Product: | LibreOffice | Reporter: | Matthijs Kooijman <matthijs> |
Component: | WWW | Assignee: | Not Assigned <libreoffice-bugs> |
Status: | RESOLVED FIXED | QA Contact: | |
Severity: | trivial | ||
Priority: | medium | CC: | beimaginativeegroup, cloph, floeff, LibreOffice, programming, qubit, steve |
Version: | unspecified | ||
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | BSA ProposedEasyHack DifficultyBeginner SkillJavaScript TopicWeb | ||
i915 platform: | i915 features: | ||
Attachments: | Mockup for additional heading with hint |
Description
Matthijs Kooijman
2012-05-07 06:21:00 UTC
Yes, especially on <https://www.libreoffice.org/bugzilla/> it's difficult to understand that the bugzilla login is the same as for <bugs.freedesktop.org> I think an additional line in the ASSISTANT heading should be enough Current text: "Thank you for ... This assistant will lead you step by step through the bug report process. " Should be something like "Thank you for ... This assistant will lead you step by step through the bug report process at bugs.freedesktop.org." I can't tell whether there is an easy solution to add a single line frame <https://www.libreoffice.org/bugzilla/> with a hint "Freedesktop.org Bugzilla via Libreoffice Bugzilla assistant" similar to the mockup Created attachment 61150 [details]
Mockup for additional heading with hint
Please do not use https://www.libreoffice.org/bugzilla/*, use https://bugs.freedesktop.org/* URLs instead.. Thanks Florian R. So is this Resolved? I don't thinks so: None of the urls in my original report show any indication that these bugzilla's are the same. Matthijs: Are you sure this is not fixed? I see: http://cl.ly/image/2y452U2Z3m2Q which clearly states log in with your "bugzilla account". So that part is fixed. I agree that having both https://www.libreoffice.org/bugzilla/ and https://bugs.freedesktop.org/ is confusing. Imo if https://bugs.freedesktop.org/ is the one to be used, we should either forward https://www.libreoffice.org/bugzilla or remove that. Any thoughts? Should we adjust the title? Florian? Joren? (In reply to comment #6) > Matthijs: Are you sure this is not fixed? > > I see: http://cl.ly/image/2y452U2Z3m2Q which clearly states log in with your > "bugzilla account". So that part is fixed. The problem is not that it is unclear that a bugzilla account is involved - The problem is that it is unclear _which_ bugzilla is involved. Because everything links to https://www.libreoffice.org/bugzilla/, there is no way to know that you are supposed to log in with a bugs.freedesktop.org account. > I agree that having both https://www.libreoffice.org/bugzilla/ and > https://bugs.freedesktop.org/ is confusing. That is the actual bug I was reporting, yets. > Imo if https://bugs.freedesktop.org/ is the one to be used, we should either > forward https://www.libreoffice.org/bugzilla or remove that. Forwarding would make sense to me, if that is possible. CC: Qubit: Do you happen to know, who could take care of that forwarding option? Setting to NEW. (In reply to comment #8) > CC: Qubit: Do you happen to know, who could take care of that forwarding > option? Setting to NEW. Floeff or Cloph would be the names at the top of my list. The libreoffice.org/bugzilla URL exists as a helper-URL for the BSA, so I'm not sure exactly what we could/should do to change it: https://wiki.documentfoundation.org/QA/BSA/Implementation#System_Administration (I'll cc: Rob on this bug, as he knows a lot more about the BSA than I) Adding cloph and floeff to CC. It seems that httpS://www.libreoffice.org/bugzilla/ already worked before I've now set a redirection up for httP://www.libreoffice.org/bugzilla/ Can you confirm it works as expected? This looks fixed to my eyes. Please re-open if you disagree and specify further steps. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.