LOSA override to disable select groups from "contact this user/group" feature
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Triaged
|
Low
|
Unassigned |
Bug Description
The problem:
we are starting to see requests that are using the contactuser feature as a "back door" to funnel SA-style requests to the LOSA's.
This is bad as it bypasses the entire CHR apparatus, and also requires us to ask a submitter to re-submit their question via Answers for correct tracking/
It'd be tricky to pull off, but I am personally loathe to trust emailed requests of that nature for what are often destructive actions against projects/branches etc.
Trust for contact is one thing; trust for destructive project requests is something else.
The proposal:
That a flag (or whatever) be able to have select groups not show the feature; or be disabled for them if 'not showing' is too tricky.
I have no problem being contacted privately about my projects; but being contacted this way for LOSA tasks is inappropriate use of this facility. I suspect there are other groups that'd be much the same. eg Registry.
Thoughts?
Changed in launchpad-registry: | |
importance: | Undecided → Wishlist |
status: | New → Triaged |
tags: | added: contact-via-web |
Non-team member have no reason to send a message to every team. The feature will (for the next release) send a message to the team owner, who may choose the answer the message, delegate it, or ignore it.