QA/BugTriage/Pre-Written Responses

    From The Document Foundation Wiki
    < QA‎ | BugTriage

    TDF LibreOffice Document Liberation Project Community Blogs Weblate Nextcloud Redmine Ask LibreOffice Donate

    Introduction

    This wiki page is to list pre-written responses that bug triagers can use when responding to a bug reporter's bug description or comments. These responses can be integrated within your browser by means of an extension (Firefox, Chrome/Chromium/Opera) so that you dont have to copy/paste it constantly from this webpage.

    Confirming A Bug

    Hello [user's name],

Thank you for reporting the bug. I can confirm that the bug is present in master.

Version: 4.4.0.0.alpha0+
Build ID: b6da6a887a0417be02e123a6d19837123e58b94f
TinderBox: Linux-rpm_deb-x86@45-TDF, Branch:master, Time: 2014-08-09_07:47:21

    Request A Sample Document

    Hello [user's name],

Thank you for reporting the bug. Please attach a sample document, as this makes it easier for us to verify the bug. 
I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' once the requested document is provided.
(Please note that the attachment will be public; remove any sensitive information before attaching it. 
See <https://wiki.documentfoundation.org/QA/FAQ#sanitize> for help on how to do so.)

    Request For Clearer Steps

    Hello [user's name],

Thank you for reporting the bug.
Unfortunately without clear steps to reproduce it, we cannot track down the origin of the problem.
Please provide a clearer set of step-by-step instructions on how to reproduce the problem.
I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' once the steps are provided

    Request For Retesting in the latest version of Libreoffice

    Hello [user's name],

Thank you for reporting the bug.
It seems you're using an old version of LibreOffice.
Could you please try to reproduce it with the latest version of LibreOffice
from <https://www.libreoffice.org/download/download-libreoffice/> ?
I have set the bug's status to 'NEEDINFO'. Please change it back to
'UNCONFIRMED' if the bug is still present in the latest version.

    Request For Retesting in Master

    Hello [user's name],

Thank you for reporting the bug. Unfortunately I can't reproduce in

Version: 5.3.0.0.alpha0+
Build ID: 8974b0fafb18f9dd3f2c0e175a3255b80e4c249e
CPU Threads: 4; OS Version: Linux 4.2; UI Render: default; 
Locale: ca-ES (ca_ES.UTF-8); Calc: group

Could you please try to reproduce it with a master build from <https://dev-builds.libreoffice.org/daily/master/current.html> ?
You can install it alongsidethe standard version.
I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the master build

    Possible Duplicate Bug

    Hello [user's name],

Thank you for reporting the bug. Can you see if bug XXXX is similar to your problem so that I can mark your report as a duplicate of it? (Later bugs are generally marked as duplicates of earlier bugs).

    Confirmed Duplicate Bug

    Hello [user's name],

Thank you for reporting the bug. This issue has previously been reported, so this bug will be resolved as a duplicate of the earlier report. You will automatically be added to the CC list of the other bug.

    Test with brand new profile

    Hello [user's name],

Thank you for reporting the bug. To be certain the reported issue is not
related to corruption in the user profile, could you please reset your
Libreoffice profile (<https://wiki.documentfoundation.org/UserProfile>) and
re-test?

I have set the bug's status to 'NEEDINFO'. Please change it back to
'UNCONFIRMED' if the issue is still present

    Request for User to Submit Backtrace (Windows)

    Unfortunately it hasn't been possible for me to reproduce the crash. If possible, please follow the instructions provided at this link <https://wiki.documentfoundation.org/How_to_get_a_backtrace_with_WinDbg> and submit a backtrace. That way a developer can look into the underlying reason of the crash.

    Request for User to Submit Backtrace (Linux)

    Unfortunately it hasn't been possible for me to reproduce the crash. If possible, please follow the instructions provided at this link <https://wiki.documentfoundation.org/QA/BugReport/Debug_Information#GNU.2FLinux> and submit a backtrace. That way a developer can look into the underlying reason of the crash.

    Request for User to Submit Screencast

    Unfortunately it hasn't been possible for me to reproduce the problem with the provided instructions. If possible, create and attach a screencast showing the steps. There are various free screencast software available for use, including Camstudio (Windows), Jing (Mac), Simple Screen Recorder (Linux) or screencast-o-matic.com (Web).

    Request for User File From Online Location

    Unfortunately our bug tracking system only permits the submission of files under 10 MB. Please host your file at one of the online file hosting service such as Dropbox, Box.com, Google Drive, or OneDrive and provide us with a link to the file.

    Request User Not Reply to Bugzilla From Email

    Note: Please do not reply to messages by email as it adds unnecessary information into the bug tracking system. Instead, click on the bug number link provided in the email, login to Bugzilla, and add comments and attachments.
    Note: Please click on the bug number link provided in the e-mail and you will be taken to this bugzilla page, where you can add comments and attachments.
    Retrieved from "https://wiki.documentfoundation.org/index.php?title=QA/BugTriage/Pre-Written_Responses&oldid=771858"