A good to help developers find out what is going wrong with a bug is providing as much information as possible. Sometimes this information is available, but distributed over multiple bug trackers. This task is to look for duplicates in other bug trackers, e.g.: https://bugs.launchpad.net/ubuntu/+source/libreoffice https://bugzilla.novell.com/buglist.cgi?query_format=specific&order=relevance+desc&bug_status=__open__&product=&content=libreoffice https://bugzilla.redhat.com/buglist.cgi?query_format=specific&order=relevance+desc&bug_status=__open__&product=Red+Hat+Enterprise+Linux+6&content=libreoffice and link to them in the 'see also:' field on this bugzilla (and also on the other bugzilla, if possible).
*** Bug 47656 has been marked as a duplicate of this bug. ***
adding LibreOffice developer list as CC to unresolved EasyHacks for better visibility. see e.g. http://nabble.documentfoundation.org/minutes-of-ESC-call-td4076214.html for details
Migrating Whiteboard tags to Keywords: (easyHack, difficultyBeginner, topicQA)
JanI is default CC for Easy Hacks (Add Jan; remove LibreOffice Dev List from CC) [NinjaEdit]
Not my scope
Hi, in which language are we advised to write this script ? I guess it is supposed to run in a web server ? It seems possible to make request to launchpad api and used bugzilla api (i hope) regards,
(In reply to Regis Perdreau from comment #6) > Hi, in which language are we advised to write this script ? I guess it is > supposed to run in a web server ? It seems possible to make request to > launchpad api and used bugzilla api (i hope) > regards, This is not about a script, but manual work.
Hello, I am new to LibreOffice Foundation and want to work on this bug. Do you mean, I have to manually check whether someone else also reported a similar type of bug on all platforms and link them? I went through this webpage, https://wiki.documentfoundation.org/QA/BugReport so here it's clearly mentioned that some bugs need to be reported outside Bugzilla. So, that means the users made a glitch here(by reporting a bug on the wrong platform)? As it's already been clarified by them which type of bug should be reported where. By the way, I would really like to work on this bug. If you can also guide me a bit, it would be really helpful to me.
(In reply to Harshita Nag from comment #8) > Hello, I am new to LibreOffice Foundation and want to work on this bug. Do > you mean, I have to manually check whether someone else also reported a > similar type of bug on all platforms and link them? Yes, but note that this is a very low-priority task for QA. If you want to get into QA, please email me and we can schedule a discussion (as I do with everyone) > I went through this webpage, > https://wiki.documentfoundation.org/QA/BugReport so here it's clearly > mentioned that some bugs need to be reported outside Bugzilla. > So, that means the users made a glitch here(by reporting a bug on the wrong > platform)? As it's already been clarified by them which type of bug should > be reported where. No, that is not what this is about. This is about linking upstream (TDF Bugzilla) to downstream (bug trackers of various Linux distros). This can include any tracker you can find with a web search, not only the ones listed by Björn in 2012 (and novell.com is not active anymore anyway).
Ok sure:) I have emailed you.
Re-evaluating the EasyHack in 2022 This task is still relevant. There are still some information available on Ubuntu bug tracker regarding LibreOffice: Ubuntu Libreoffice package: (sorted, newest first) https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bugs?orderby=-id&start=0 One may work on the above bugs. If reproducible, and already available on Bugzilla, add its url in "see also" field. If not, but still reproducible, add it as a new bug, and then fill "see also" field.