Bug 151410 - "Please report this incident." is not actionable advice
Summary: "Please report this incident." is not actionable advice
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: UI (show other bugs)
Version:
(earliest affected)
7.5.0.0 alpha0+
Hardware: All All
: lowest trivial
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Redaction
  Show dependency treegraph
 
Reported: 2022-10-07 16:30 UTC by Tuomas Hietala
Modified: 2025-02-24 03:10 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Tuomas Hietala 2022-10-07 16:30:10 UTC
Description:
In sfx2/messages, there's the following string: "An error occurred while adding new target. Please report this incident."

The "Please report this incident." part is not really actionable advice, though, because it doesn't say _where_ the incident should be reported to.



Steps to Reproduce:
1. See https://translations.documentfoundation.org/translate/libo_ui-master/sfx2messages/en/?checksum=d8a6cd840ab8b6ea


Actual Results:
The string does not specify where to report the incident, possibly disconcerting the user for no good reason.

Expected Results:
The string either gives useful information to the user, or is deleted.


Reproducible: Always


User Profile Reset: No



Additional Info:
n/a
Comment 1 Aron Budea 2022-10-29 01:54:56 UTC
Just collecting some information, this is a string of a message that might be shown in a message box in the Tools -> Auto-Redact dialog.

It was first added in the following commit:
https://cgit.freedesktop.org/libreoffice/core/commit/?id=fe977ec07087b103de8c809597fdaea8dd629837
(and got converted to a translatable string later)
Comment 2 Aron Budea 2022-10-29 01:56:46 UTC
Help for Auto-Redact: https://help.libreoffice.org/latest/en-US/text/shared/guide/auto_redact.html
Comment 3 QA Administrators 2025-02-24 03:10:34 UTC
Dear Tuomas Hietala,

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 https://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://web.libera.chat/?settings=#libreoffice-qa

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

Warm Regards,
QA Team

MassPing-UntouchedBug