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
F2969962: D25476.1739523773.diff
Thu, Feb 13, 09:02
F2962640: D25476.1739181407.diff
Sun, Feb 9, 09:56
F2962639: D25476.1739181403.diff
Sun, Feb 9, 09:56
F2961487: D25476.1739163561.diff
Sun, Feb 9, 04:59
F2947272: D25476.1738451597.diff
Fri, Jan 31, 23:13
F2937331: D25476.1737951704.diff
Sun, Jan 26, 04:21
F2937308: D25476.1737950943.diff
Sun, Jan 26, 04:09
F2937305: D25476.1737950896.diff
Sun, Jan 26, 04:08

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