To avoid having unassigned work in progress, we should have the ability to create new triggers under the columns, similar to what exists now, but instead of assigning to a concrete user, we should be able to assign to the person who has performed the column movement.
Context: https://www.mediawiki.org/wiki/Phabricator/Project_management#Automated_actions_via_column_triggers
Upstream: https://we.phorge.it/T16058
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Stalled | Feature | Aklapper | T393464 New Column Trigger: Assign only unassigned tasks | ||
| Resolved | Feature | Aklapper | T393268 New Column Trigger: When moving to a column, assign to the "current user" (user that is performing the move) | ||
| Resolved | Aklapper | T393840 Update to Phorge upstream rPca176821 / Arcanist upstream rARCd2d2afd0 (2025-09-08) | |||
| Resolved | brennen | T404134 Merge Phorge's upstream master (2025-09-08) into our wmf/stable |
I want to reflect here on an implicit requirement (making it explicit), as the problem that we want to solve is (quoting myself on the description)
To avoid having unassigned work in progress
The issue should be unassigned
Trigger rules don't allow setting any conditions when to trigger.
Supporting a check whether the issue was previously unassigned will probably need to be a separate rule / condition; something like "Assign unassigned task to..."
I'd say split into a separate feature request task and make it depend on this one. :)
This issue should now be fixed on phabricator.wikimedia.org after today's software deployment in T404134.