Bug 84472 - Deal with UNCONFIRMED NeedAdvice Bugs
Summary: Deal with UNCONFIRMED NeedAdvice Bugs
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: contrib (show other bugs)
(earliest affected)
Hardware: Other All
: medium normal
Assignee: Not Assigned
URL: https://redmine.documentfoundation.or...
Keywords: topicQA
Depends on:
Reported: 2014-09-29 16:07 UTC by Björn Michaelsen
Modified: 2019-12-03 14:21 UTC (History)
0 users

See Also:
Crash report or crash signature:


Note You need to log in before you can comment on or make changes to this bug.
Description Björn Michaelsen 2014-09-29 16:07:28 UTC
QA is now aggressively getting through unconfirmed bugs but we do have the NeedAdvice bugs that are just kind of hanging out. What would be nice is for Robinson to do "whatever is necessary" -- meaning he himself communicate with the user to diagnose, ping whatever developer might be able to help, etc... to move these forward. I believe he's already started doing this but I think it can be now a "routine task" for the QA Engineer.

That being said - we'll try to keep the # manageable so it's not a huge time suck. Also not a really high priority generally.
Comment 1 Björn Michaelsen 2014-09-29 16:09:44 UTC
migrated from https://redmine.documentfoundation.org/issues/594 (which we cannot add to "see also" here, which is sad).
Comment 2 QA Administrators 2015-10-14 19:57:09 UTC Comment hidden (obsolete)
Comment 3 Robinson Tryon (qubit) 2015-12-10 11:18:45 UTC Comment hidden (obsolete)
Comment 4 QA Administrators 2017-01-03 19:41:34 UTC Comment hidden (obsolete)
Comment 5 QA Administrators 2019-12-03 14:21:52 UTC
Dear Björn Michaelsen,

To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not 
appropriate in this case)

If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword

Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team