Page MenuHomePhabricator

Don't require any special capabilities to apply a "closed a subtask" transaction to a parent task
ClosedPublic

Authored by epriestley on Feb 28 2019, 4:09 PM.
Tags
None
Referenced Files
F19565117: D20223.diff
Jan 31 2026, 5:59 PM
F19527876: D20223.diff
Jan 19 2026, 5:04 AM
F19225537: D20223.diff
Dec 17 2025, 8:14 PM
F19153334: D20223.diff
Dec 11 2025, 9:04 AM
F19121636: D20223.id.diff
Dec 9 2025, 10:30 PM
F19082931: D20223.id48297.diff
Dec 2 2025, 12:27 PM
F18985052: D20223.id48283.diff
Nov 17 2025, 12:51 PM
F18881952: D20223.id.diff
Nov 6 2025, 10:15 PM
Subscribers
None

Details

Summary

See PHI1059. If you close a task, we apply an "alice closed a subtask: X" transaction to its parents.

This transaction is purely informative, but currently requires CAN_EDIT permission after T13186. However, we'd prefer to post this transaction anyway, even if: the parent is locked; or the parent is not editable by the acting user.

Replace the implicit CAN_EDIT requirement with no requirement.

(This transaction is only applied internally (by closing a subtask) and can't be applied via the API or any other channel, so this doesn't let attackers spam a bunch of bogus subtask closures all over the place or anything.)

Test Plan
  • Created a parent task A with subtask B.
  • Put task A into an "Edits Locked" status.
  • As a user other than the owner of A, closed B.

Then:

  • Before: Policy exception when trying to apply the "alice closed a subtask: B" transaction to A.
  • After: B closed, A got a transaction despite being locked.

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable