Page MenuHomePhabricator

GlobalRenameRequest: Allow to suppress rename requests
Open, MediumPublic

Description

There is an unused rq_deleted field on the renameuser_queue table but the feature has not been implemented yet.

Event Timeline

Glaisher raised the priority of this task from to Needs Triage.
Glaisher updated the task description. (Show Details)
Glaisher added a project: GlobalRename.
Glaisher subscribed.
Ajraddatz triaged this task as Medium priority.Apr 25 2016, 7:25 PM
Ajraddatz subscribed.

Set to normal priority. No/few cases of needed use so far, but should be built in.

Yes, this would be useful for cases where the name contains private information or other suppressable material according to policy. Thanks.

We're running from time to time into cases that requires this feature. Could some resources be allocated to enable it? It's kinda user-unfriendly to ask an op to mess manually in the DB to remove the row. Thanks!

Yes, this would be useful for cases where the name contains private information or other suppressable material according to policy. Thanks.

I started looking in to this a bit. What exactly would you want to be able to delete - the request reason? The old name? The new name? The notes added by the global renamers? Also, should there be two levels of deletion, normal and suppression, or just one? (No promises that I'll be able to find the time to work on this, but would be good to know anyway what the desired feature is)

Reason and new name definitely need to be suppressable. Notes are stored on public wiki pages, and should be handled by the existing system. I don't think a level below suppression is needed.