Page MenuHomePhabricator

Disable auto-assigning IABot tasks to Cyberpower678
Closed, ResolvedPublic0 Story Points

Description

Due to Herald rule H204 ("InternetArchiveBot auto-assign Cyberpower678"), all and any InternetArchiveBot tasks get assigned to the single individual @Cyberpower678.
This creates a huge (and unrealistic) backlog of tasks assigned to @Cyberpower678 (currently 73 open tasks, see https://phabricator.wikimedia.org/maniphest/query/V1o_G1nEHmTj/#R) which sometimes remain open for years.

Auto-assigning tasks to an individual is an anti-pattern. Such cookie-licking (see 1 and 2) creates wrong expectations to end users that someone will work on their task of interest.
It might also make other potentially interested developers not contribute: Others do not assign any task to themselves, as it looks like all tasks are already being worked on as all tasks already have an assignee.

I propose to remove the "auto-assign" part from Herald rule H204.

Event Timeline

Aklapper created this task.Jun 30 2019, 8:38 PM
Restricted Application assigned this task to Cyberpower678. · View Herald TranscriptJun 30 2019, 8:38 PM
Aklapper moved this task from To Triage to Herald rules on the Phabricator board.

I am the only developer of the bot, and until more developers would like to join in and assist me, I see no reason to remove this rule as I'm the only one that ends up acting on them.

Aklapper added a comment.EditedJul 20 2019, 9:28 PM

I am the only developer of the bot, and until more developers would like to join in and assist me, I see no reason to remove this rule as I'm the only one that ends up acting on them.

Thanks for your reply!

If you claim every task, though you might not realistically work on every task for quite some time, there obviously will be no more developers who would like to join because interested people will not find any unassigned tasks that they could work on, as it looks like you work on every task.
So the current pattern creates a self-fulfilling prophecy.
And that is problematic, hence I filed this task, as the statement that you personally are really going to "end up acting" on all those tasks sounds a bit unrealistic to me (given the number of open tasks)?

Plus you seem not to be the only one that ends up acting on them (Example)?

@Cyberpower678: Could you explain why it's so important for your workflow to be assigned to all tasks? How do you organize what you plan to work on and how does the assignee field influence that? I'd like to understand why project workboards or search functionality might not be sufficient for you but that you seem to rely so heavily on the assignee field.
For example, if you are after receiving notifications about changes in IABot tasks, see https://www.mediawiki.org/wiki/Phabricator/Help#Receiving_updates_and_notifications how to watch a project and how to adjust your notification preferences in Phab.

I see your point. I will alter the herald task to simply subscribe me. The idea was that I'm immediately made aware of any new task or changes to tasks concerning my bot.

Cyberpower678 closed this task as Resolved.Jul 20 2019, 10:22 PM

I see your point. I will alter the herald task to simply subscribe me.

Thanks a lot!

The idea was that I'm immediately made aware of any new task or changes to tasks concerning my bot.

You can still have that, without being task assignee. :) And if you need any help with Herald rules or notifications settings, please let me know!
(You may also want to unassign from some tasks if you don't plan to actively work on them in the future, to have a more realistic list of tasks when you go to https://phabricator.wikimedia.org/maniphest/query/assigned/ )

Oh, and instead of "Add rule author as subscriber", you could watch the project instead.