QA/Bugzilla/AutomatedTasks

This page is about the Automated tasks of Bugzilla using the bugzillaChecker script

= Checks =

Running the script
 * 1) Download bugzilla_dump.json from vm174.documentfoundation.org:/home/esc-mentoring/esc/dump/bugzilla_dump.json ( this script can be used: https://redmine.documentfoundation.org/attachments/download/1937/downloadBugzillaDump.sh )
 * 2) Run './bugzillaChecker.py' (https://cgit.freedesktop.org/libreoffice/contrib/dev-tools/tree/qa/bugzillaChecker.py)

The script will warn of the following problems:

movedToFixed

 * Problem: The reporter has moved the bug to RESOLVED FIXED.
 * Solution: The bug should be moved to RESOLVED WORKSFORME unless there's a commit fixing it.

autoConfirmed

 * Problem: The reporter has auto-confirmed his/her own bug.
 * Solution: The bug should be moved back to UNCONFIRMED unless the reporter intends to work on it.

newerVersion

 * Problem: Someone has changed the version field to a newer one.
 * Solution: Version field should be changed back to the previous version unless the previous version was incorrect. Check history to see the previous version.

crashSignature

 * Problem: In order to link Bugzilla with http://crashreport.libreoffice.org, the crashreport field should have the format ["-signature-"], otherwise it doesn't work.
 * Solution: Change the crashreport field to the correct format

addAssigned

 * Problem: Someone has changed the Assignee field and it's different to the default one ( libreoffice-bugs@lists.freedesktop.org ) but the status is not set to ASSIGNED.
 * Solution: Set the status field to ASSIGNED.

removeAssigned

 * Problem: Someone has changed the assignee field to the default one ( libreoffice-bugs@lists.freedesktop.org ) but the status is still ASSIGNED
 * Solution: Change the status back to NEW

addAssignee

 * Problem: Someone has changed the status field to ASSIGNED but the assigne is still the default one ( libreoffice-bugs@lists.freedesktop.org ).
 * Solution: Change the assignee field accordingly

removeAssignee

 * Problem: Someone has changed the status field from ASSIGNED to NEW but the assignee field is still different to the default one ( libreoffice-bugs@lists.freedesktop.org )
 * Solution: Assignee field should be changed to the default one ( libreoffice-bugs@lists.freedesktop.org )

backPortAdded

 * Problem: Someone has added the whiteboard 'backport' but the bug's status is still NEW
 * Solution: Status field should be changed to RESOLVED

fixBugPing

 * Problem: The last comment is from 'libreoffice-commits@lists.freedesktop.org' and it was done more than a month ago.
 * Solution: Leave the following comment:

A polite ping to : Is this bug fixed? if so, could you please close it as RESOLVED FIXED ? Otherwise, Could you please explain what's missing? Thanks

inactiveAssigned

 * Problem: The bug has been in ASSIGNED status for more than 3 months without any activity.
 * Solution: Change the status to NEW and reset the assignee to default. Leave a comment like:

Dear [developer-name], This bug has been in ASSIGNED status for more than 3 months without any activity. Resetting it to NEW. Please assigned it back to yourself if you're still working on this.

emptyAlias

 * Problem: a metabug doesn't have an alias. Having an alias is always good because it makes things more easy visually speaking.
 * Solution: Add an alias describing the metabug

New Contributor

 * Problem: a new contributor has signed up in Bugzilla and he/she has interacted in 3 or more bugs.
 * Solution: Send a welcome email to the new contributor:

Subject: Welcome to the LibreOffice community!!

Body: Hello [name], On behalf of the QA Team, I would like to give you a warm welcome to the LibreOffice project and express my sincere gratitude for your contributions in our bugtracker[1]. As you might know, LibreOffice depends on volunteers like you to keep the software alive & improving and any help is much appreciated. In the QA team, we identify problems in our software, confirms problems reported by users, and validates proposed fixes and enhancements so each new version of LibreOffice is more reliable and robust. You can find more information about QA in our wiki page[2] and the most 'bleeding edge' version of LibreOffice can be downloaded from here[3]. If you need to contact us, you can do it via IRC [4], Telegram [5] or the mailing list [6]. Keep up the good work. Regards [1]. https://bugs.documentfoundation.org/ [2]. https://wiki.documentfoundation.org/QA [3]. https://dev-builds.libreoffice.org/daily/master/ [4]. https://wiki.documentfoundation.org/QA/IRC [5]. https://t.me/LibreOffice_QA [6]. https://wiki.documentfoundation.org/QA/Mailing_List

Inactive Contributor

 * Problem: an old contributor who interacted in more than 20 bugs in the past has been inactive for more than 6 months
 * Solution: Send them a 'we miss you' email

Subject: LibreOffice: We miss you!

Body: Hello [name], I'm writing you this email on behalf of the LibreOffice QA Team to express my sincere gratitude for your past contributions to the project. As you might know, LibreOffice depends on volunteers like you to keep the software alive & improving and we really appreciate your work. We have noticed your activity in Bugzilla has stopped for some time now and we know volunteering is something most of us do in our spare time, so it is normal to have periods where you need to concentrate on other items, however, we would love to have you back whenever you have time again. On the other hand, if there is anything we can do to help you with, we would love to hear it. Thanks in advance

patchAdded

 * Problem: A patch has been attached to bugzilla along with the keyword 'patch'
 * Solution: Ask the user to submit the patch to gerrit instead. Message:

Dear [user-name], Thanks for the patch. Could you please submit it to gerrit as described here: https://wiki.documentfoundation.org/Development/gerrit/SubmitPatch?

reopened6Months

 * Problem: A bug has been fixed for more than 6 months and it has been reopened
 * Solution: Close the bug as RESOLVED FIXED and ask the user to open a new issue. Message:

Dear [user-name], This bug has been in RESOLVED FIXED status for more than 6 months. If the issue is still reproducible with the latest version of LibreOffice from https://www.libreoffice.org/download/libreoffice-fresh/, please report a new issue in https://bugs.documentfoundation.org/enter_bug.cgi providing, if    needed, the steps and documents to reproduce it. Thanks for your understanding and collaboration. Closing as RESOLVED FIXED

movedToNeedInfo

 * Problem: A bug has been confirmed ( NEW ) and someone moves it to NEEDINFO. In general, NEEDINFO should only be used for UNCONFIRMED bugs.
 * Solution: Change the status accordingly. Normally, either change it back to NEW or change it to RESOLVED.

reopened

 * Problem: A bug has been moved to REOPENED but it was never set to RESOLVED FIXED before. In general, REOPENED, should be only used for FIXED bugs.
 * Solution: Change the status accordingly. Normally, change it to NEW

regressionAdded

 * Problem: regression keyword has been added to a bug without anything else ( bibisected, bisected, bibisectNotNeeded, bibisectRequest, notBibisectable, preBibisect ).
 * Solution: Add the needed keyword. In general it would be bibisectRequest but it might be other depending on the comments

= Automated tasks =

Running the script
 * 1) Download bugzilla_dump.json from vm174.documentfoundation.org:/home/esc-mentoring/esc/dump/bugzilla_dump.json ( this script can be used: https://redmine.documentfoundation.org/attachments/download/1937/downloadBugzillaDump.sh )
 * 2) Run './bugzillaAutomation.py' (https://cgit.freedesktop.org/libreoffice/contrib/dev-tools/tree/qa/bugzillaAutomation.py)

Obsolete comments
Automatically mark as obsolete the following type of comments when they are not the last comment in the bug:
 * 1) 'Untouched for a year' comments
 * 2) Cleaning-out needinfo comments
 * 3) Cleaning-out needinfo follow-up comments
 * 4) Comments starting with 'A polite ping, still working on this bug'

Bug untouched for a year
Ping bug reports with no update for one year or more. Exclude: Any [Meta], [Task] and [Super] bugs, EasyHacks, ux-advise bugs (with keyword needsUXEval) and enhancement requests

Stock Message
Dear [reporter's name], 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://irc.documentfoundation.org/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug

NEEDINFO: First notification
Find NEEDINFO bugs that haven't changed in 180 days and point users to the NEEDINFO page, request information again and let user know that if requested information is already there, to appropriately set the status of the bug so we move the bug forward

Stock Message
Dear [Reporter's Name], This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping

NEEDINFO: Follow-up Message 30 days later
30 Days after the first notification close the bug as INSUFFICIENTDATA because of lack of information and let user know that if they are still experiencing the bug they can open it back up as UNCONFIRMED if they provide requested information

Stock Message
Dear [Reporter's Name], Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating   system and the latest version of LibreOffice that you have    confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details   on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp