Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Encourage all readers, not just requesters, to report delivery errors #5640

Closed
RichardTaylor opened this issue Apr 24, 2020 · 1 comment
Closed
Labels
easier-admin Make issues easier to resolve f:classifications improvement Improves existing functionality (UI tweaks, refactoring, performance, etc) stale Issues with no activity for 12 months

Comments

@RichardTaylor
Copy link

We don't currently encourage third parties to send admin teams reports of delivery errors via the "Actions" -> "Report this request" route, adding a new category there to cover reports of "Error messages or delivery problems" might help.

We do encourage requesters themselves to flag up delivery errors when classifying their own requests.

The classification form only becomes available to others after a long period of time has elapsed, any reports of error messages made then are not timely.

The primary way the WhatDoTheyKnow.com admin team catches delivery errors is by having alerts set up for terms which appear in delivery errors / bounce messages. Some error messages don't trip such alerts. The circumstances which have led to this ticket being raised have been also been addressed by expanding the set of terms alerts are set for, this is another idea for helping ensure issues are flagged up with administrators.

There is some risk of duplicate reports if we both have automated alerts and encourage manual reports. Hopefully administrators will deal promptly with automated alerts and manual reports would be made in any missed cases.

Screenshot 2020-04-24 at 12 08 48

Screenshot 2020-04-24 at 12 09 39

@HelenWDTK
Copy link
Contributor

This issue has been automatically closed due to a lack of discussion or resolution for over 12 months.
Should we decide to revisit this issue in the future, it can be reopened.

@HelenWDTK HelenWDTK closed this as not planned Won't fix, can't repro, duplicate, stale Nov 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
easier-admin Make issues easier to resolve f:classifications improvement Improves existing functionality (UI tweaks, refactoring, performance, etc) stale Issues with no activity for 12 months
Projects
None yet
Development

No branches or pull requests

3 participants