Page MenuHomePhabricator

Set default assignee for WMDE-Technical-Writing
Closed, InvalidPublic



Please set the default assignee for the project "WMDE-Technical-Writing" to me, "danshick-wmde". (I received a hint that this somehow requires a Herald rule, though I know nothing of them.)

Event Timeline

Restricted Application added a subscriber: Aklapper. · View Herald TranscriptOct 14 2020, 8:17 AM
Kizule edited projects, added Phabricator; removed Project-Admins.Oct 14 2020, 8:26 AM
danshick-wmde added a subscriber: Kizule.EditedOct 14 2020, 9:08 AM

Maybe I've already succeeded in doing this thanks to @Kizule 's suggestions in T265448 ...

Kizule closed this task as Resolved.Oct 14 2020, 9:11 AM
Kizule assigned this task to danshick-wmde.

This is done by @danshick-wmde in {H374} and works (tested with T265458).

Kizule moved this task from To Triage to Herald rules on the Phabricator board.Oct 14 2020, 9:11 AM
Aklapper reopened this task as Open.EditedOct 14 2020, 10:27 AM

@danshick-wmde: Please do not do this and please disable this Herald rule.

Auto-assigning is a classic anti-pattern in software development: All and any tasks get assigned to one single person, no matter if that single person will ever realistically be able to work on a task or not, however for outsiders it looks like that person is going to work on a task. This anti-pattern leads to many tasks "assigned" for years without any progress (see e.g. T228575). This anti-pattern does exist in reality (see e.g. T241152 for one example) and blocks other people from working on tasks or helping with tasks.

Please revert.

Also see how to get notifications / follow projects.

danshick-wmde closed this task as Invalid.Oct 14 2020, 10:47 AM
danshick-wmde triaged this task as Lowest priority.

I've done as you requested. I respectfully request that if Herald allows functionality that is rejected by organizational policy, that functionality should be disabled if possible or at least red-flagged on the page that enables it, or on .

Technical writing is not software development, and I believe different groups use Phabricator in different ways, but I will adhere to tool-wide organizational policy and only ask that it be more clearly and consistently presented.