Page MenuHomePhabricator

Remove "Action Has No Effect" warning dialog when removing auto assigned user
Closed, ResolvedPublic

Description

Upstream: https://we.phorge.it/T15164

Currently unassigned tasks will get the user executing the action assigned when the task is marked as resolved. If you do not want that so happen and remove yourself in the step, you'll get a warning message, that you one of your actions has no effect.

It would be really nice to at list have this message removed or suppressed in that use case. It's annoying and not quite correct in that case.

P.S.: Maybe this task will be invalid when [V22] will lead to removing the auto assignment in the first place.

Event Timeline

Aklapper renamed this task from Avoid the "Action with no effect" warning when removing the auto assigned user to Remove "Action Has No Effect" warning dialog when removing auto assigned user.May 19 2023, 10:03 AM
Aklapper triaged this task as Medium priority.EditedMay 19 2023, 10:06 AM

Makes sense to me. That's src/applications/transactions/response/PhabricatorApplicationTransactionNoEffectResponse.php and src/applications/transactions/response/PhabricatorApplicationTransactionNoEffectResponse.php in https://gitlab.wikimedia.org/repos/phabricator/phabricator

Should probably check the editengine.actions JSON for {"type":"status","value":"resolved","initialValue":null} && {"type":"owner","value":[],"initialValue":[]} and not trigger when owner value and initialValue are still the same.

Aklapper updated the task description. (Show Details)
Aklapper moved this task from Backlog to Upstreamed on the Phabricator (Upstream) board.
Aklapper moved this task from Backlog to Reported Upstream on the Upstream board.
Aklapper changed the task status from Open to Stalled.Mar 17 2024, 4:49 PM
Aklapper moved this task from Upstreamed to Solved upstream on the Phabricator (Upstream) board.
Aklapper moved this task from Patch proposed upstream to Patch merged upstream on the Upstream board.

Fixed in upstream; setting status to Stalled as this is now waiting for a new upstream release and us to pull and deploy it

This should have gotten resolved by today's deployment pulling and deploying the 2024.19 upstream version. If not, please comment.