Page MenuHomePhorge

Avoid "Action with no effect" for auto-claim statuses after manually removing assignee
AbandonedPublic

Authored by aklapper on Nov 24 2023, 21:42.
Tags
None
Referenced Files
F3335631: D25476.1743565033.diff
Tue, Apr 1, 03:37
F3335380: D25476.1743562346.diff
Tue, Apr 1, 02:52
F3331251: D25476.1743504366.diff
Mon, Mar 31, 10:46
F3327390: D25476.1743438555.diff
Sun, Mar 30, 16:29
F3322133: D25476.1743365081.diff
Sat, Mar 29, 20:04
F3320819: D25476.1743338031.diff
Sat, Mar 29, 12:33
F3318869: D25476.1743292323.diff
Fri, Mar 28, 23:52
F3318435: D25476.1743284468.diff
Fri, Mar 28, 21:41

Details

Summary

Remove the reassign transaction from $results as we de-facto do not change the task owner: it was unset before and will be unset after, so there is no transaction to perform.

Closes T15164

Test Plan

tbd - This is still WIP

Diff Detail

Repository
rP Phorge
Branch
T15164 (branched from master)
Lint
Lint Passed
Unit
Tests Passed
Build Status
Buildable 951
Build 951: arc lint + arc unit

Event Timeline

(Test plan contains "tbd - This is still WIP" - please mark as such)

Thanks again for this proposed solution. I have now a big picture and I partially agree on the approach: the fix is there, in touching the manually-set claim action, but maybe we can just mute that "non-effective manual transaction" instead of dropping it. And anyway, we can maybe recycle some code about finding that transaction.

Edited: also it's maybe better to keep that $is_claim definition only in the inner case. That probably had sense for micro-optimization reasons.

I'm personally OK with this solution, premising that we can maybe review this instead that has the above suggestions (I was not able to express these using voice):

D25550: Avoid "Action with no effect" for auto-claim statuses after manually removing assignee