Page MenuHomePhabricator

Freeze "maniphest.gettasktransactions" and make status/priority transactions more consistent
ClosedPublic

Authored by epriestley on Nov 22 2017, 2:15 PM.
Tags
None
Referenced Files
Unknown Object (File)
Fri, Apr 19, 2:43 AM
Unknown Object (File)
Thu, Apr 11, 8:25 AM
Unknown Object (File)
Sat, Apr 6, 7:04 AM
Unknown Object (File)
Sun, Mar 31, 1:57 PM
Unknown Object (File)
Fri, Mar 29, 10:29 AM
Unknown Object (File)
Feb 26 2024, 3:25 PM
Unknown Object (File)
Feb 24 2024, 5:04 PM
Unknown Object (File)
Feb 10 2024, 6:41 PM
Subscribers
None

Details

Summary

Ref T13020. See PHI221.

Freeze legacy method maniphest.gettasktransactions in favor of modern method transaction.search.

Remove legacy "null on create" behavior from Maniphest status and priority transactions. This behavior is obsolete with EditEngine, and leads to inconsistent transaction sets in the transaction record.

The desired behavior is that transactions which don't do anything (e.g., default value was not changed) don't appear in the transaction log.

Test Plan
  • Viewed API UI and saw maniphest.gettasktransactions marked as "Frozen".
  • Created a new task via web UI (without changing status/priority), queried transactions with maniphest.gettasktransacitons/transaction.search, no longer saw "null on create" no-op transactions in record.
    • Web UI is unchanged, since these transactions were hidden before and now do not exist.

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable